3,620,411 launches on record
Coverage from 2 Sep 2026
Archive read 06:28 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-03 05:18 UTC

PUMPDOG

PumpDog

7QGwoxPhy7U2oaEi7Wj8XR1K5S4Ak1u6KcJj9iSkpump 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 five lists, or with Brand Protection at $79 a month for every list on every record. 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

34.8%of supply taken by the creator in the first block
22outside wallets bought on the bonding curve
Noreached a graduation threshold while we watched
The creator took 35% 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 30 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.

31launches on record from this creator wallet, this one included, over 6 days
10on 3 Sep, its busiest day
30different tickers; the one it used most is BADSHREK, 2 times
3 Sep: 109 Sep: 510 Sep: 111 Sep: 512 Sep: 714 Sep: 3
3 SepThis creator wallet's launches per day (UTC)14 Sep
Its most recent other launches (UTC)TickerNameMint
14 Sep, 04:12MIKESEM The Black Tyson██████████
14 Sep, 03:53HORIZON Mike Horizon██████████
14 Sep, 01:14BFARAOH Batonkammon██████████
12 Sep, 10:25BUNDLEINU Bundle Inu██████████
12 Sep, 09:39EVILDOGE Do Only Evil Everyday██████████
12 Sep, 09:15Castle Castlecoin██████████
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 34.8% of supply at launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-03 05:18 UTC
CreatorEcnh3z12Rgqi6YMQqXy8bmRgXXsfLvjvsYe3ow4kW8bx
Creator took34.8% of supply in the first block
Outside buyers22 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.
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 from3bioVVXRNAHVS2wQRrEsXW… slot 443,889,182
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-03 05:18:09 UTC
Slot 443,889,182, 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.
Highest price seen2026-09-03 05:24:47 UTC +6m 38s
7.912e-8 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 340 launches from 296 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 creator30 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 →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 1 other creator wallet, across 2 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

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
NamePumpDog
Metadata heldsha256 aa0bb1be6f6bd61bd56172859194e2fcdb1694c2564e78c60f7eef85f2ae561e · 179 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 bfd33a7a86d5c8ea4c08664db8e2b5fedc9da88acdff5e789c3307e36b3bf184 · 436,064 bytes

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