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

PAIDAPE

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 picture is on 4 other launches from 2 creator wallets in all, and this creator has 19 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. Across the archive, 44.3% 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.

2KpT3StvdhVRNDynzaj4vFup3zecMzwpLPN7LpKtpump 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.

At launch

Created2026-09-15 22:34 UTC
Creator2VYNgBhhfeGFfMfCuejUwK4P3Tb6N5yJ4NsyTrY33jxW
Creator took1.7% of supply in the first block
Outside buyers15 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: 2 within the first 30s, 0 in the very same block the token was created in.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldyes
Recorded from4v2bkqtivfFfqnWZmkZwxW… slot 447,364,643
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-15 22:34:11 UTC
Slot 447,364,643, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in2 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.
Highest price seen2026-09-15 22:38:03 UTC +3m 52s
4.116e-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.

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 5 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 15 launches from 9 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 creator19 earlier launches. All 1 that reached the graduation threshold on our feed were read on chain, and none had completed. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 1 other creator wallet, across 2 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 of 2 creator wallets in all. See the linked wallets →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NamePAIDAPE
Metadata heldsha256 c02a5d1f69b77c5449f08b5e562f0680b28089fa11e1ecef8b64e2ef586ca1e7 · 296 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 3380c4da70d55825d893537b75bc3a6712da68b37a172479756814c70934b514 · 139,124 bytes

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