Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all, and this creator has 5 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
At launch
| Created | 2026-09-02 18:26 UTC |
| Creator | 8X1LcB9j11GV3npf6mC5zMtK24hQszq8acCiQk6cEw9Z |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 10 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: 7 within the first 30s, 2 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 | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | not while we watched |
| Recorded from | Not recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked. |
Order of events
| Created | 2026-09-02 18:26:28 UTC |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-02 18:26:28 UTC
3.698e-8 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 | 7 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 | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 978 launches from 668 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 5 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
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 | STONKS |
| Description | nasdaq go up. stonks go up. elonmusk favorite meme |
| Metadata held | sha256 c51f3cf0b2625d3276bd24825725ea6efe579ae7b7f2e37b068cb0784de45043 · 390 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 26b0cb43f63a18b95d8638d95a3d3064f5a1112312d5b1915f4931842920e4ad · 48,494 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 22:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.