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

CRACK

The curve completed 27s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

FVyDMVgabFdMmZU93162UQGuZkUjjgf18FVctztWpump Solscan pump.fun
findingOnly 4 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 27s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-28 23:26 UTC
CreatorFajP2FjmdGDxPwbhVStVVEkMQ2sC2nEayypBztviPfNM
Creator took0.7% of supply in the first block
Outside buyers4 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 0 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.4 days ago and it was finished. Checked 2026-09-29 14:33 UTC.
Creator soldyes
Recorded from4hv6B61bq4ayvKMuv5jQoJ… slot 451,466,211
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-28 23:26:06 UTC
Slot 451,466,211, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-09-28 23:26:34 UTC +27s
Confirmed against the venue's own completion state.
Thirty seconds in4 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-28 23:26:37 UTC +30s
3.698e-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 21 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 93 launches from 54 creator wallets, including this one. See them →
This creator25 earlier launches, 1 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. 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
NameCrack cocaine coin
Metadata heldsha256 b6cb4800545183bf8de6bd57b1acb249aafcaa251e747156f2f734c86fcdf876 · 305 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-29 23:26 UTC.
Picture heldsha256 143d46ebabb0dccc714ca9e6640105ce135357e414969c3cdbd7add05bbf3b99 · 215,114 bytes

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