3,717,261 launches on record
Coverage from 2 Sep 2026
Archive read 13:20 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-16 09:01 UTC

mihao

ni hao cat

Dv8HNFS2P31KG3po9FuHbZaBm2PJePwErcVYkGE4pump Solscan pump.fun

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

11.2%of supply taken by the creator in the first block
109outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

Also recorded, and not part of the finding above: this picture is on 50 other launches from 36 creator wallets in all. 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.5% 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.

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

At launch

Created2026-11-16 09:01 UTC
Creator6agmM1LjdbnUB73ueB1B5uzwBfYB5aXyuDRuYypSwaoR
Creator took11.2% of supply in the first block
Outside buyers109 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: 46 within the first 30s, 20 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.
Graduated3 min 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 from9adB32oyz5p4bjQTL3rhcn… slot 470,073,637
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-11-16 09:01:06 UTC
Slot 470,073,637, which is the chain's own clock for this moment.
Creation block20 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in46 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 completed2026-11-16 09:04:01 UTC +2m 54s
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 38 launches from 36 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 936 launches from 686 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.7% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity0.9 SOL
Read from chain2026-11-16 13:52 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Nameni hao cat
Descriptionyou met me at a very chinese time in my life
Metadata heldsha256 9793571fe177eba8229219a7832fca8ee2ffb4ed2294d94d544037bdf1c3080f · 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 a8448ae5074db7cfa86fd8f3d8b07202502cb3fe1bd762daebbc06a6a6948822 · 476,026 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-16 09:01 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