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

ULTRA

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

6wVHR4iBTnxoBfkk6nheXkxavyfap28cL1zFgxFNpump Solscan pump.fun
findingOnly 7 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 9s after launch.

At launch

Created2026-10-02 15:00 UTC
Creator5FAwzUoCr4TgrVdwENKqtsgubswmEzS427QaPhVG7Pav
Creator took0.9% of supply in the first block
Outside buyers7 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 0 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 5.4 h ago and it was finished. Checked 2026-10-02 17:01 UTC.
Creator soldnot while we watched
Recorded from2BxD2v8TQhep6BwAjC9Teu… slot 452,644,413
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 15:00:33 UTC
Slot 452,644,413, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-02 15:00:41 UTC +9s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 15:00:48 UTC +15s
1.287e-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 in7 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 1,616 launches from 299 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 1,684 launches from 331 creator wallets, including this one. See them →
This documentByte-identical to 1,598 other launches' metadata document. See them →
This creator77 earlier launches, 3 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 5 other creator wallets, across 4 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
NameULTRAPAID
Metadata heldsha256 356de6a0e0df31c4e9bd4d3069af2f7b8a77490eacc02345828709a7b0e132df · 192 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 a45d05459adda2c9a252564cf5dbd8d8b4b0b7cedf60e94e98533b2bbb0cf75e · 248,878 bytes

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