3,636,637 launches on record
Coverage from 2 Sep 2026
Archive read 13:17 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-10-31 19:03 UTC

SUPER

Superpad

8DKHFW32ApiG6xLYrTDTxkWMGxdDyASfNnSaWwCbpump Solscan pump.fun

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

5.2%of supply taken by the creator in the first block
8outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed in the same batch of events as the 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 2 other launches from 3 creator wallets in all. 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.5% 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.

findingOnly 8 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 1.5 SOL of liquidity was in the pool just now.

At launch

Created2026-10-31 19:03 UTC
CreatorG1uKPbFCCrTyvdJdekzkEY5ZDqATe5kTmqxXCUQyNLHR
Creator took5.2% 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: 8 within the first 30s, 8 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.
Graduated0 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 from22eJDYscinGtd2i9VUDCVQ… slot 463,799,119
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-31 19:03:09 UTC
Slot 463,799,119, which is the chain's own clock for this moment.
Creation block8 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-31 19:03:09 UTC +0s
Confirmed: a PumpSwap pool was found for it.
Thirty seconds in8 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.
Highest price seen2026-10-31 19:04:30 UTC +1m 20s
1.134e-6 SOL per token. Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a decoded one. 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 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 664 launches from 400 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.6% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 2 other launches, across 3 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 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.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity1.5 SOL
Read from chain2026-11-14 20:02 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameSuperpad
DescriptionThe launch venue for super intelligences. Every agent has a coin, a job, and a wallet. $SUPER is the house.
Metadata heldsha256 b3141a777c9c6b82af88c7f528b1381c9d6cc83eab920bf278846ecf7d18073b · 374 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-11-07 19:03 UTC.
Picture heldsha256 6ea7a3cc3517d358c67c4b33aa733a52b75fcc757547ff05afd83d8626da4b01 · 137,577 bytes

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