1,125,634 launches on record
Coverage from 2 Sep 2026
Archive read 19:04 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

PUD

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

3EGTUhUhPDT1V2C9fL51yDbD9Pzf255RoWPNgPnzpump Solscan pump.fun
findingIt left the curve 15s after launch.

At launch

Created2026-09-28 21:44 UTC
CreatorB2PxDJS58DV4SWRnq96muyUrt7kRqVK5EK8DF39Zoig6
Creator took0.2% of supply in the first block
Outside buyers37 distinct wallets, not counting the creator, bought on the bonding curve: 8 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.3 days ago and it was finished. Checked 2026-09-29 15:03 UTC.
Creator soldnot while we watched
Recorded fromSi1GmcyjviiY9H4YeiAUDt… slot 451,443,477
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-28 21:44:35 UTC
Slot 451,443,477, 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 21:44:50 UTC +15s
Confirmed against the venue's own completion state.
Highest price seen2026-09-28 21:45:05 UTC +30s
3.036e-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.
Thirty seconds in8 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.

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 18 launches from 9 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 13 launches from 10 creator wallets, including this one. See them →
This creator62 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. 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
NamePUD
Metadata heldsha256 db52318747c44f69744d7a673f9d1316120240d7d58c4733f92b195631df2c47 · 288 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 21:46 UTC.
Picture heldsha256 00bf922cdcb2a6bd654b4069af91888edfb1477bd99772f82ea42335eee58131 · 11,182 bytes

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