Its own first blocks
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-13 22:03 UTC |
| Creator | 5YS3jhvmWzuW9SpHkHb6ZdVnefaSh2Rgt2733TCBfY7P |
| Creator took | 0.5% of supply in the first block |
| Outside buyers | 3 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: 2 within the first 30s, 1 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 | 1.8 h 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 | Yy4d1NQBEW3dFsoixAcWn6… slot 469,086,626
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-13 22:03:42 UTC Slot 469,086,626, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 2 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. |
| Curve completed | 2026-11-13 23:52:11 UTC +1h 48m 30s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-13 23:52:31 UTC +1h 48m 50s
1.411e-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. |
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 | GTA6 HYPE TRAIN |
| Description | Who's ready for GTA 6???? IM READY!!! LETS GOOOOO!!!! What was your first GTA game??? |
| Metadata held | sha256 59ab2441e32575ad12aac3563c1e44d351b749edc43e50be02b906a7d74259ea · 389 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 df443d458c6f01c384dbbd0d06406a4e2f3b95621e1a2c536887c1231d40afc8 · 173,559 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-13 22:03 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.