Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-11-12 12:26 UTC |
| Creator | 3jxjPygmUtaEy8aBNJzcZc3YaiszcrueAPjVrp6QWZHe |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 5 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 5 within the first 30s, 5 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 0 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 4tNDBCCUxoS7mL9Kj95fTL… slot 468,524,873
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-12 12:26:53 UTC Slot 468,524,873, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-12 12:26:57 UTC +4s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-12 12:26:57 UTC +4s
4.109e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 5 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | No other launch we hold a picture for used this one. |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | GRAND THEFT ORBIO |
| Description | Vice City was just the beginning. Now we're taking over the orbit. |
| Metadata held | sha256 f1a661a7cccc1a1f2e97658de74e660d05a3d1b04c3d82d9fbace0040fab5d08 · 386 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Picture held | sha256 be82629ff1a4f09a121b9750e7dcec570830eb907fb3eca96eba9ff76fcb903f · 1,222,834 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 12:26 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.