MAYHEM
The curve completed 14s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
findingIt left the curve 14s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 09:18 UTC |
| Creator | 4akzn48fR1Dv5HkViUDzdS3x8M9PuTbiAoYQGXasdPjs |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 25 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 3kaUucpufokcAgxesbWab7… slot 452,567,500
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 09:18:44 UTC Slot 452,567,500, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-10-02 09:18:58 UTC +14s Confirmed: a PumpSwap pool was found for it. |
| 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. |
| Highest price seen | 2026-10-02 09:19:14 UTC +30s
4.173e-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 | On 4 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 504 launches from 77 creator wallets, including this one. See them → |
| This creator | 4 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-02 19:25 UTC, just now |
What this launch claimed to be
| Name | MAYHEM |
| Description | Welcome to MAYHEM. No roadmap. No promises. Just Solana, degens, green candles, red candles, and absolute chaos. You either send it or watch from the sidelines. |
| Metadata held | sha256 8402b0f14fc9851057eadcecacee5ae752d17817bf374675ece5488e41acfbe2 · 454 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 d607f8b0c805c9e4e3647a1b257b41b2b8721b64d2b8e83cc8c450d76a920c19 · 527,432 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 09:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.