532,304 launches on record
Coverage from 2 Sep 2026
Archive read 14:14 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

PIP

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

HD3efjXnaJPXP28pzEBBjUJgyj7UJWGmL9hSJHp2pump Solscan pump.fun
findingIt left the curve 33s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-19 11:35 UTC
Creator9uexVyJAwtVwicjNCorqXRZoWVYotXvE8AGjPYvd8XXm
Creator took0.4% of supply in the first block
Outside buyers46 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 4.9 h ago and it was finished. Checked 2026-09-19 12:48 UTC.
Creator soldyes
Recorded from2NAftKgHxCRVRMXKFECAw6… slot 448,395,720
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-19 11:35:28 UTC
Slot 448,395,720, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in5 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-19 11:36:01 UTC +33s
Confirmed against the venue's own completion state.
Highest price seen2026-09-19 11:36:50 UTC +1m 22s
4.135e-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 3 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 45 launches from 37 creator wallets, including this one. See them →
This creator23 earlier launches, 0 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
Namepip world
Metadata heldsha256 f4ac795df786b947911e839b4e118aba8e6d2200ff1d43ff2623a382a76a5a57 · 360 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 e2120718e61c7a06e8ddc92b018f83fd4345bbdbc14cdae7819a48903c1b9b34 · 91,923 bytes

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