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

NFA

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 creator has 25 other launches 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.

AcnBcR3WxMoinjrVZnvKhaZeEYzxCSvTuBunnzxspump Solscan pump.fun

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.

noteThe creator sold while we were watching.
noteOnly 2.0 SOL of liquidity was in the pool just now.

At launch

Created2026-09-14 05:08 UTC
Creator4wwGjJeSsepdewUgiJAMieBn1ydobFdqZHwpo7uvq4JD
Creator took10.0% of supply in the first block
Outside buyers502 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: 119 within the first 30s, 13 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.
Graduated14 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 soldyes
Recorded fromJjttScu7caqzZFA8FaQvzT… slot 446,892,854
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-09-14 05:08:08 UTC
Slot 446,892,854, which is the chain's own clock for this moment.
Creation block13 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in119 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-09-14 05:22:10 UTC +14m 03s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-14 05:22:10 UTC +14m 03s
4.109e-7 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 41 launches from 36 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 →
This creator25 earlier launches, 3 confirmed complete on chain. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 7 other creator wallets, across 12 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

Liquidity2.0 SOL
Read from chain2026-10-03 06:31 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameNever Fade Again
DescriptionI'll be Going Live on PumpFun Introducing NFA Never Fade Again After this coin you will Never Fade Again, KOL's will prove their motion by buying into this coin and mooning the fuck out of it, Never Fade a good community Again I will get the dex at 15k, and boost at marketcap goals
Metadata heldsha256 d254e82cda3f6bac6dce7d69841069d2242a174663ab4abe25ae2602c998da1c · 587 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-21 23:44 UTC.
Picture heldsha256 84f10a96702e1a8d80fec3df1f44649b6edcddf0d2755509525e2d905b9bbf03 · 1,952,728 bytes

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