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

bandit

No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.

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.

CnjCdk9YmpVM63LpYiLGNfUpPH3ws7XrYqk7YEDTpump Solscan pump.fun
noteThe creator sold while we were watching.

At launch

Created2026-09-30 18:54 UTC
CreatorA3wSqxeAWXQDYjsY8UzueURJ6jrxuWiv1xjLfsWhgbZU
Creator took8.2% of supply in the first block
Outside buyers60 distinct wallets, not counting the creator, bought on the bonding curve: 12 within the first 30s, 4 bundled into the creation block.
Graduated5 min after launch
Curve, read on chainComplete. We read the bonding curve account 3.6 h ago and it was finished. Checked 2026-09-30 19:02 UTC.
Creator soldyes
Recorded from2PJE2vWb18wkVABBmbSYXH… slot 452,051,059
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-30 18:54:22 UTC
Slot 452,051,059, which is the chain's own clock for this moment.
Creation block4 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in12 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-30 18:59:23 UTC +5m 01s
Confirmed against the venue's own completion state.
Highest price seen2026-09-30 18:59:23 UTC +5m 01s
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.

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
NameThe PumpFun Heist
DescriptionThe PumpFun Heist
Metadata heldsha256 0ec325417cff5d2cccfd243d464f98f2693020fd34544d7c8fb027854fda621e · 258 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 4bdc692b767a69bb2666dc5ef13662fce009cd4e351a4477d1dd414a3070cc58 · 392,049 bytes

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