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

CRYPT

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 5 other launches from 5 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, 46.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.

2rjEFhbkKdxf2g4UWBsB4S35yaQrync4BAnSq3HTpump 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 1.9 SOL of liquidity was in the pool just now.

At launch

Created2026-10-05 15:51 UTC
CreatorTQKhxsbzEVq9Ak23XbD8XVR8NFanUDGWUE3QGgz1EvU
Creator took1.8% of supply in the first block
Outside buyers635 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: 252 within the first 30s, 9 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.
Graduated3 min after launch
Curve on chainComplete. We read the bonding curve account 1.2 days ago and it was finished. Checked 2026-10-05 16:01 UTC.
Creator soldyes
Recorded from3DWhdr6PzQrEKPwNXJHvHk… slot 453,624,625
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-05 15:51:17 UTC
Slot 453,624,625, which is the chain's own clock for this moment.
Creation block9 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in252 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-05 15:54:11 UTC +2m 55s
Confirmed against the venue's own completion state.
Highest price seen2026-10-05 15:54:11 UTC +2m 55s
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 pictureOn 6 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 46.4% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 178 launches from 93 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, 86.3% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 5 other launches, across 5 creator wallets in all. Across the archive, 23.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 4 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. Across the archive, 57.8% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity1.9 SOL
Read from chain2026-10-06 19:58 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameCrypt
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 caa94de8fee4eb8ea8dbc8683346b5c60067b280317c7a9a6a71e7ad7cf8281b · 352 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-10-06 18:03 UTC.
Picture heldsha256 3c86c102f382b1a8b84ac8b2ceeab5dbee914ed4768d88a5c46c457cac93e90b · 9,568 bytes

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