1,359,819 launches on record
Coverage from 2 Sep 2026
Archive read 18:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

Build

Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 1.0%, 548 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 7 other launches from 8 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, 45.4% of the launches whose picture we hold carry one a different creator also used. 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.

AXxRj2uiUPq8ggiRPD8EdYzbj1vKQxuxtFDAQHPkpump Solscan pump.fun

At launch

Created2026-10-04 12:58 UTC
CreatorDPftrtiCnPuf9p9B2pnF6zZ5zt5snWzFnFWpKcPxPTpv
Creator took1.0% of supply in the first block
Outside buyers548 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: 113 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.
Graduated6 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 from4kNMiNv7qZj2mYvC9idQsc… slot 453,263,332
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.

Order of events

Created2026-10-04 12:58:36 UTC
Slot 453,263,332, 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 in113 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-04 13:05:04 UTC +6m 27s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-04 14:35:49 UTC +1h 37m 13s
1.923e-6 SOL per token. Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a decoded one. 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 pictureOn 8 launches from 8 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 79 launches from 74 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. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 7 other creator wallets, across 3 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. See the linked wallets →

Pool

Liquidity125.4 SOL
Read from chain2026-10-04 21:15 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameBuild
Metadata heldsha256 3828fd207dc8557699e90c9c93e28bca74dfbcae540af8262b8d0ec5f6649740 · 278 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 a26692de08d83213da9a00fd1ae30a5dd8b98f004fa22e70b8d85f5d94d307f5 · 747,452 bytes

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