Also recorded, and not part of the finding above: this picture is on 70 other launches from 32 creator wallets in all, and this creator has 3 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.4% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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-06 13:59 UTC |
| Creator | BGNoh1Bfwk8rLdUnm5nKRJ55U6cWYeqTTakNdDEH8G2k |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 5 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: 5 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 | 0 min after launch |
| Curve 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 | 5DnTwBmBdzKdFEhetVQM7r… slot 466,134,943
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-06 13:59:10 UTC Slot 466,134,943, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-06 13:59:10 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-06 13:59:10 UTC +0s
4.109e-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. |
| Thirty seconds in | 5 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 71 launches from 32 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.4% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 410 launches from 245 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 | 3 earlier launches, 3 confirmed complete on chain. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches → |
Who took the curve
One transaction bought 42 SOL of this curve, 0 min after launch, from a wallet other than the creator's. The wallet and the transaction →
Pool
| Liquidity | 9.6 SOL |
| Read from chain | 2026-11-13 08:19 UTC, just now |
What this launch claimed to be
| Name | MAMESUKE |
| Description | MAMESUKE was launched on StonkFun. |
| Metadata held | sha256 d73a2b4d04d702bf222e7a2f72a2c3299477f1931d518fea8b674efd60d9836d · 331 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-11-10 02:41 UTC. |
| Picture held | sha256 9b10280dae61da2641a5057a263e2cd7278af1d3c53931653761243ba429f162 · 64,307 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-06 13:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.