3,513,749 launches on record
Coverage from 2 Sep 2026
Archive read 06:31 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-13 20:51 UTC

BILLION

Billion

GEaPJ5FY3zY9y9SK6fEeL6X8bNGdvCTT1fnB51xQpump Solscan pump.fun
26.6%of supply taken by the creator in the first block
816outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
110launches carry this ticker, from 91 creator wallets
1other launch declared this same launch document, byte for byte
5other launches used this exact picture file
The creator took 27% of supply at launchRead 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 picture is on 5 other launches from 3 creator wallets in all, and this creator has 362 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, 56.3% of the launches whose picture we hold carry one a different creator also used. 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.

noteThe creator took 26.6% of supply at launch.
noteOnly 5.5 SOL of liquidity was in the pool just now.

At launch

Created2026-09-13 20:51 UTC
Creator69aiAKU3uJMxMLRkUEGFNt6nQ43PiVimE4ZbErJ7VSM1
Creator took26.6% of supply in the first block
Outside buyers816 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: 212 within the first 30s, 7 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.
Graduated4 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 from5cd1qGN3hynN8sK7VXwh4G… slot 446,798,477
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-13 20:51:31 UTC
Slot 446,798,477, which is the chain's own clock for this moment.
Creation block7 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in212 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-13 20:55:53 UTC +4m 22s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-14 12:00:48 UTC +15h 09m 17s
0.000e+0 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 6 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 110 launches from 91 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 documentThe same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them →
This creator362 earlier launches, 20 confirmed complete on chain, 1 with findings on record. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 189 other creator wallets, across 337 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity5.5 SOL
Read from chain2026-11-12 12:29 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameBillion
DescriptionIntroducing $BILLION, the first project paired with itself.
Metadata heldsha256 87143277aec0146cdcfd92ba3424f6cd49a8e2a256f2fd6f5053ed4380de4177 · 460 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-22 00:10 UTC.
Picture heldsha256 a27920bdda6ea7b403371f0e251f8654cd74bebcf11f43fc0fb94220b43ff770 · 42,001 bytes

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