2,416,505 launches on record
Coverage from 2 Sep 2026
Archive read 25 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

mihao

Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 15.4%, 60 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this creator has 1 other launch 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. They are listed under Seen before, further down this page.

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.

4CxjZyMNoF1p6eXHXHv1TWpS2X47CuUmLwtGe18spump Solscan pump.fun

Cite this record as: Chain of Title, mihao (ni hao cat), mint 4CxjZyMNoF1p6eXHXHv1TWpS2X47CuUmLwtGe18spump, observed at creation 2026-10-25 13:27 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/4CxjZyMNoF1p6eXHXHv1TWpS2X47CuUmLwtGe18spump

At launch

Created2026-10-25 13:27 UTC
Creator9tH2zRYdS3X7PEcsPno3GST1EHe8GX8CSNih1pKpamAp
Creator took15.4% of supply in the first block
Outside buyers60 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: 1 within the first 30s, 2 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.
Graduated6.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 from3TeNATBbcgiXbNFRf4RF7p… slot 461,274,116
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-25 13:27:41 UTC
Slot 461,274,116, which is the chain's own clock for this moment.
Creation block2 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in1 distinct buyer, 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-10-25 13:31:56 UTC +4m 15s
8.714e-8 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-10-25 19:33:57 UTC +6h 06m 16s
Confirmed against the venue's own completion state.

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 pictureNo other launch we hold a picture for used this one.
This creator1 earlier launch, none of which reached a graduation threshold while we watched. Across the archive, 70.2% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity65.4 SOL
Read from chain2026-10-26 05:41 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 9e74ef6ebde4881de037f6b0b26093c99073c64c523cb0b54c246cefdf6c80f6 · 360 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 b92cb6fbd647f633327b19f6c50fd6d4e52f091d2c409d00def016a4a88c0115 · 120,504 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-25 13:27 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