3,739,960 launches on record
Coverage from 2 Sep 2026
Archive read 20:11 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-02 18:25 UTC

all/in

My pronouns are all/in

5KZUh7teDXkxgTerDQR2io6CtMRky7ybcWstWiBTpump 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

20.8%of supply taken by the creator in the first block
816outside wallets bought on the bonding curve
Noreached a graduation threshold while we watched
The creator took 21% 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 creator has 47 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.

48launches on record from this creator wallet, this one included, over 25 days
9on 9 Sep, its busiest day
43different tickers; the one it used most is CRYPTO, 3 times
2 Sep: 13 Sep: 16 Sep: 27 Sep: 38 Sep: 19 Sep: 910 Sep: 211 Sep: 212 Sep: 114 Sep: 115 Sep: 316 Sep: 217 Sep: 122 Sep: 123 Sep: 124 Sep: 125 Sep: 126 Sep: 229 Sep: 51 Oct: 12 Oct: 13 Oct: 113 Oct: 214 Oct: 219 Oct: 1
2 SepThis creator wallet's launches per day (UTC)19 Oct
Its most recent other launches (UTC)TickerNameMint
19 Oct, 17:25? ?██████████
14 Oct, 20:00BOT GROKBOT██████████
14 Oct, 16:00Muse Muse██████████
13 Oct, 20:06SIRIUS The bitcoin cat██████████
13 Oct, 17:52ORBIT orbit██████████
3 Oct, 13:37swordcat swordcat██████████
See all of this creator's launches →

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 20.8% of supply at launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-02 18:25 UTC
CreatorD8n8Dy6DWC9691mR4NroSA9TdxXBxDV6Rr639RapanS4
Creator took20.8% 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: 361 within the first 30s, 6 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.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldyes
Recorded from57DfZfC23oA3TgDpLWh1Ty… slot 443,764,786
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-02 18:25:46 UTC
Slot 443,764,786, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Highest price seen2026-09-02 18:25:46 UTC
1.818e-7 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.
Thirty seconds in361 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.

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 111 launches from 89 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.7% wear one that more than one creator wallet has launched. See this ticker's page →
This creator47 earlier launches, 12 confirmed complete on chain, 2 with findings on record. Across the archive, 70.7% 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 25 other creator wallets, across 31 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.6% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

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
NameMy pronouns are all/in
Metadata heldsha256 c93e724888be0835421a2dbebaf9e39531e3355ec179980eaef195b86a5db5dc · 257 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 1c182096e01b5eca7b49290390e1c980e991b7b8fa9749710c361e177db4beec · 16,241 bytes

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