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

ULTRA

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

xccS9jm229c8aLfzqgSKqPdhdqUZwRy8cgkiHnxpump Solscan pump.fun
findingOnly 3 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 57s after launch.

At launch

Created2026-09-29 18:29 UTC
Creator5FAwzUoCr4TgrVdwENKqtsgubswmEzS427QaPhVG7Pav
Creator took0.2% of supply in the first block
Outside buyers3 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 0 bundled into the creation block.
Graduated1 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 20:02 UTC.
Creator soldnot while we watched
Recorded from4Hj9r8jPftQw5jArSNnL5R… slot 451,722,667
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-29 18:29:47 UTC
Slot 451,722,667, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in1 distinct buyer, 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-29 18:30:44 UTC +57s
Confirmed against the venue's own completion state.
Highest price seen2026-09-29 18:31:16 UTC +1m 29s
1.997e-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 1,118 launches from 268 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 1,172 launches from 297 creator wallets, including this one. See them →
This documentByte-identical to 1,102 other launches' metadata document. See them →
This creator15 earlier launches, 1 confirmed graduated on chain. See the creator's launches →

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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-30 18:30 UTC.
Picture heldsha256 a45d05459adda2c9a252564cf5dbd8d8b4b0b7cedf60e94e98533b2bbb0cf75e · 248,878 bytes

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