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

ULTI

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 6 other launches, all of them this same creator's, and this creator has 21 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 16.2% of the launches whose picture we hold carry one only their own creator reused. They are listed under Seen before, further down this page.

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.

7HFEd7ezk9UtXtm6TA3JJ79hMGJoW3wJHMTLkw5ppump Solscan pump.fun

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

noteThe creator sold while we were watching.

At launch

Created2026-10-02 11:56 UTC
Creator2yMaN7nt4gEKZbhsaXSXPwhyU22nL9Doipj4sdEC6cDh
Creator took0.5% of supply in the first block
Outside buyers15 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 7 within the first 30s, 1 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated15 min after launch
Curve on chainComplete. We read the bonding curve account 6.0 h ago and it was finished. Checked 2026-10-03 00:31 UTC.
Creator soldyes
Recorded from542kkeTmCTCvFRaaT6AZLL… slot 452,602,913
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-10-02 11:56:00 UTC
Slot 452,602,913, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
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.
Curve completed2026-10-02 12:11:03 UTC +15m 03s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 12:11:42 UTC +15m 42s
1.876e-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 7 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 8 launches from 2 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. See this ticker's page →
This creator21 earlier launches. All 2 that reached the graduation threshold on our feed were read on chain, and none had completed. 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
NameIA ULTIMATE
DescriptionA NEW CONCEPT OF IA, INTEGRATION BUSINESS, SECURITY, DEVELOPMENT DEFENSE, SPACE EXPLORER
Metadata heldsha256 5e4638379f8b6467b37efda66df95aac0b8ed6693b0e413b5e221fc5d0f77f3f · 385 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 cfc0594ec6aa58fadccf0eb972f1d57a4cf35c1cf0ec5df24308d103d0851913 · 193,812 bytes

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