What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
Also recorded, and not part of the finding above: this picture is on 53 other launches, all of them this same creator's, and this creator has 121 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. They are listed under Seen before, further down this page.
| Its most recent other launches (UTC) | Ticker | Name | Mint |
|---|---|---|---|
| 14 Nov, 00:09 | First$ | 50k Mayhem coin | ██████████ |
| 14 Nov, 00:08 | First$ | 50k Mayhem coin | ██████████ |
| 4 Nov, 14:21 | First$ | 50k Mayhem coin | ██████████ |
| 23 Oct, 06:54 | First$ | Glitched Mayhem | ██████████ |
| 20 Oct, 11:45 | First$ | Mayhem Pump Bot | ██████████ |
| 16 Oct, 15:13 | First$ | Mayhem Pump Bot | ██████████ |
| See all of this creator's launches → | |||
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-09-02 13:42 UTC |
| Creator | EoqodDDzKqEGcKBuEHtkAAzs3rM2dZtoNqpgcNkyY7Zq |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 0 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 | 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 | yes |
| 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 13:42:10 UTC |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-02 13:42:10 UTC +1s
2.820e-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 | 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. |
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 54 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 1,582 launches from 1,017 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.6% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 121 earlier launches. All 6 that reached the graduation threshold on our feed were read on chain, and none had completed. 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 | assbum |
| Metadata held | sha256 d0bd79363f1b66a1abf0b037df654beeac7688be61bcfb79dd6a6427eb87210f · 175 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 d55c1823b2945d0dcc783d3f32004208eb0a8e315045902ac7983dd8f49ab309 · 901,259 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 20:52 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.