1,017,257 launches on record
Coverage from 2 Sep 2026
Archive read 28 Sep 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

CS

The curve completed 39s 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.

ADJDJB2CbYaUaVWkppPPaUpEUmAxu9Es8kVNtKKspump Solscan pump.fun
findingIt left the curve 39s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-27 21:58 UTC
CreatorGe34Lcx9YcFMhFbHAda2ePVXym4JRhw9e2Wx7dXEBiGB
Creator took5.4% of supply in the first block
Outside buyers113 distinct wallets, not counting the creator, bought on the bonding curve: 89 within the first 30s, 5 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.1 days ago and it was finished. Checked 2026-09-27 22:02 UTC.
Creator soldyes
Recorded from3AEadZwZpVZbgphMm1m2Cf… slot 451,124,466
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-27 21:58:28 UTC
Slot 451,124,466, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in89 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-27 21:59:07 UTC +39s
Confirmed against the venue's own completion state.
Highest price seen2026-09-27 21:59:07 UTC +39s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 53 launches from 47 creator wallets, including this one. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. 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
Namechicken shrimp
Metadata heldsha256 2f30ebb98a9c986eb14ed8842fa1837623ada0757409dc4b10673fbe79fa8a9d · 342 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 e078ef99719d36693dfae2abd4ea8ab6f8dbf984321b37578cd5f8564d93b0e3 · 111,292 bytes

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