0.0%of supply taken by the creator in the first block
63outside wallets bought on the bonding curve
Noreached a graduation threshold while we watched
600launches carry this ticker, from 437 creator wallets4other launches used this exact picture file
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.
Also recorded, and not part of the finding above: this picture is on 4 other launches from 5 creator wallets in all, and this creator has 26 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-04 04:10 UTC |
| Creator | V9gfsMLyRY8UZgHqJYDuZTSAqbqp6EdS3MRYNz3WNCY |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 63 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: 10 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 | 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-04 04:10:37 UTC |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 10 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. |
| Highest price seen | 2026-09-04 04:25:37 UTC +15m 00s
5.114e-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. |
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 5 launches from 5 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 600 launches from 437 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 | 26 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 → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 5 other creator wallets, across 8 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
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 | Greatest Meme Ever |
| Description | Greatest Meme Ever — deployed on the dyke |
| Metadata held | sha256 f4b561d0f23f2ad8053bd734dbc78cc8288a2eee75087cce6fca1d6eeeb912ef · 326 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 58ee785246b5dacff260ec323b2e0be3621842e3d7ee0c1c37ec636556c450e1 · 13,879 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-12 11:11 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.