3,947,331 launches on record
Coverage from 2 Sep 2026
Archive read 21:07 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-11-20 17:25 UTC

CATPOOP

Catpoop Coin

GjjKKfd4NBY2eWsCcabZy156MwTSWW43HxP59YZDpump 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

0.1%of supply taken by the creator in the first block
18outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 6s after 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 1 other launch, and this creator has 12 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.

13launches on record from this creator wallet, this one included, over 2 days
8on 19 Nov, its busiest day
8different tickers; the one it used most is BITCAT, 3 times
19 Nov: 820 Nov: 5
19 NovThis creator wallet's launches per day (UTC)20 Nov
Its most recent other launches (UTC)TickerNameMint
20 Nov, 18:35DYSON Doge Tyson██████████
20 Nov, 16:50BITCAT BitCat Coin██████████
20 Nov, 16:44BITCAT BitCat Coin██████████
20 Nov, 12:52BITCAT BitCat Coin██████████
19 Nov, 20:41DAINU Dacity Inu██████████
19 Nov, 20:30DAINU Dacity Inu██████████
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.

findingIt left the curve 6s after launch.

At launch

Created2026-11-20 17:25 UTC
CreatorGhc6EiuCuNkCAy43vsH1dw1Pnd6Y3oMdCzNV5GXRZ6Cq
Creator took0.1% of supply in the first block
Outside buyers18 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: 18 within the first 30s, 18 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 chainComplete. We read the bonding curve account 4.4 h ago and it was finished. Checked 2026-11-20 17:36 UTC.
Creator soldnot while we watched
Recorded fromfNo1LHynHFYG4TL611SXBp… slot 471,820,111
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-11-20 17:25:02 UTC
Slot 471,820,111, which is the chain's own clock for this moment.
Creation block18 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-20 17:25:08 UTC +6s
Confirmed against the venue's own completion state.
Thirty seconds in18 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 tickerOn 6 launches from 6 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.9% wear one that more than one creator wallet has launched. See this ticker's page →
This creator8 earlier launches, 4 confirmed complete on chain. 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 5 other creator wallets, across 7 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.4% 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
NameCatpoop Coin
DescriptionCharts green, coffee spilled, zero regrets—Catpoop Coin is making a mess in the crypto trenches. 🐱💩📈
Metadata heldsha256 9dde2428460be39c9b83caf97558c74cd0dad256656a12742fc096b26a572989 · 384 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 1cc5c57b247702f9029e4fc575d10a87ce62503156635eadc2609b0eea32d5e2 · 242,664 bytes

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