3,485,155 launches on record
Coverage from 2 Sep 2026
Archive read 16:55 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-11 04:12 UTC

WIF

ni hao cat Wif Hat

D1KSio12ybe6XoNoWvFJuV8FMXTW1Ypqc4rCD5A3pump Solscan pump.fun
0.0%of supply taken by the creator in the first block
20outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
1,536launches carry this ticker, from 1,159 creator wallets
1other launch declared this same launch document, byte for byte
1other launch 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 1 other launch, all of them this same creator's. 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.

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.

noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-11-11 04:12 UTC
CreatorDmPY5Mg5Lo1xDctcmCCBBsAZ12ATqadK4eMhgcoGRE19
Creator took0.0% of supply in the first block
Outside buyers20 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: 6 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.
Graduated11.1 h after launch
Curve on chainNot 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 soldnot while we watched
Recorded from2Uu3keo7uABbmnodvNxa4h… slot 467,984,754
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-11 04:12:42 UTC
Slot 467,984,754, which is the chain's own clock for this moment.
Creation block3 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in6 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 seen2026-11-11 06:42:15 UTC +2h 29m 33s
0.000e+0 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.
Curve completed2026-11-11 15:21:07 UTC +11h 08m 25s
Confirmed: a PumpSwap pool was found for it.

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 pictureOn 2 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 tickerOn 1,536 launches from 1,159 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 documentThe same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them →

Pool

Liquidity0.0 SOL
Read from chain2026-11-11 19:10 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Nameni hao cat Wif Hat
Descriptionni hao cat Wif Hat
Metadata heldsha256 e8ee30cc530b70d466a6137f9cab84f37b9c3e1cb12f4f1e3cce529bffbfe8c4 · 363 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 heldsha256 285320f49a7263a2462c9647b7ca3d862ddeab875a07d560d36227258c9f2973 · 465,056 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-11 04:12 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another