2,933,205 launches on record
Coverage from 2 Sep 2026
Archive read 03:27 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Pikmin

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.3%, 294 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 picture is on 16 other launches. 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.

2MXhpKgHBREgYYj3bSdorqbuJjkPAve1LTNHtk8Lpump Solscan pump.fun

Cite this record as: Chain of Title, Pikmin, mint 2MXhpKgHBREgYYj3bSdorqbuJjkPAve1LTNHtk8Lpump, observed at creation 2026-10-31 14:13 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/2MXhpKgHBREgYYj3bSdorqbuJjkPAve1LTNHtk8Lpump

At launch

Created2026-10-31 14:13 UTC
Creator9V31X2bQcAepDGnwirYixGJJbXEimvdo33HjfRjSj6tJ
Creator took15.3% of supply in the first block
Outside buyers294 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: 127 within the first 30s, 6 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.
Graduated4 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 from33VWTft9KPs3NTvVWCc23C… slot 463,717,888
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-31 14:13:05 UTC
Slot 463,717,888, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in127 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-10-31 14:16:57 UTC +3m 52s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-31 15:10:30 UTC +57m 26s
1.651e-6 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 tickerOn 3 launches from 3 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, 88.4% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity110.3 SOL
Read from chain2026-10-31 16:04 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NamePikmin
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 33b0c975d428da3726bd296bdd6f4710a57bb317ea4d7a54037bd1101dfa3c73 · 391 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 3e628eaa4ad2f8aa1f09f286333eb831b07b2aaace1716bde1a077852b353c72 · 38,294 bytes

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