3,485,057 launches on record
Coverage from 2 Sep 2026
Archive read 16:55 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-09-05 10:49 UTC

EXIT

HDXnPsGEoGRbRZKNWJv5yBsHtMLTsRct2CtsH2u8pump Solscan pump.fun
1.0%of supply taken by the creator in the first block
8outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
438launches carry this ticker, from 242 creator wallets
Only 8 outside buyers bought its curveRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this creator has 3 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. They are listed under Seen before, further down this page.

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.

findingOnly 8 outside buyers bought on the bonding curve before it graduated.
noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-09-05 10:49 UTC
Creator83E7Ph51sXRTipaL9V7r3pwDA33YFxkbk8r1RVQ66orJ
Creator took1.0% of supply in the first block
Outside buyers8 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: 0 within the first 30s, 0 in the very same block the token was created in.
Graduated37 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from4wiMASzUTpX2vy67p39S7J… slot 444,500,460
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-05 10:49:16 UTC
Slot 444,500,460, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds inNo 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-05 11:26:09 UTC +36m 53s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-05 11:26:10 UTC +36m 54s
0.000e+0 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 438 launches from 242 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. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page →
This creator3 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity0.0 SOL
Read from chain2026-11-11 18:55 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameEXIT
DescriptionEveryone is selling. I'm not
Metadata heldsha256 9bee9bdd0e319a31eff018dfd0ab9b60edc07fff80424af3e6b6d14c8524c112 · 201 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-19 18:29 UTC.
Picture heldsha256 e37e577aede60973f69e35e25828a890d8264580add48c66e0a660828d1842ad · 369,461 bytes

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