0.1%of supply taken by the creator in the first block
331outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
334launches carry this ticker, from 271 creator walletsNo 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.
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.
noteThe creator sold while we were watching.
noteOnly 1.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-27 00:44 UTC |
| Creator | CsyVBQgEmdi155YKWqaKb7DNmkznBALsBaUu3z2hhH3D |
| Creator took | 0.1% of supply in the first block |
| Outside buyers | 331 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: 81 within the first 30s, 3 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 | 15 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 | yes |
| Recorded from | 3Q4o9DzMV6RCjuwov85ah8… slot 450,839,313
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-27 00:44:28 UTC Slot 450,839,313, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 81 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. |
| Curve completed | 2026-09-27 00:59:39 UTC +15m 11s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-27 00:59:39 UTC +15m 11s
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. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 334 launches from 271 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 → |
Pool
| Liquidity | 1.5 SOL |
| Read from chain | 2026-11-12 16:25 UTC, just now |
What this launch claimed to be
| Name | Nyan Cat |
| Description | Fees to @NyanCat via UsePaid |
| Metadata held | sha256 cf552e0450a8e6a8ac4523248b543a90eabbb351a9de7f762ae9a60bf1182dc3 · 292 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-10-04 00:44 UTC. |
| Picture held | sha256 962a379a4cd5e26365d4d2f5ca164fe271dd7d975103163c1eaccddc69babe81 · 34,836 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-27 00:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.