3,625,592 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-11-11 03:57 UTC

CATE

Cate

tqiZmkGj528NRyvUT2YtiHKZxkwGNudE5iW25sspump 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

26.6%of supply taken by the creator in the first block
8outside wallets bought on the bonding curve
Noreached a graduation threshold while we watched
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 18 other launches from 3 creator wallets in all, and this creator has 39 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.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.

40launches on record from this creator wallet, this one included, over 5 days
19on 15 Oct, its busiest day
28different tickers; the one it used most is PAIN, 4 times
15 Oct: 1919 Oct: 13 Nov: 110 Nov: 211 Nov: 17
15 OctThis creator wallet's launches per day (UTC)11 Nov
Its most recent other launches (UTC)TickerNameMint
11 Nov, 04:04FINALMAYHE THE FINAL MAYHEM██████████
11 Nov, 04:01Blitz Blitz Coin██████████
11 Nov, 03:59Alight Alight Coin██████████
11 Nov, 03:55CATE Cate██████████
11 Nov, 03:53CC Croydon Coin██████████
11 Nov, 03:51rayan Rayan Coin██████████
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 26.6% of supply at launch.
noteThe creator sold while we were watching.

At launch

Created2026-11-11 03:57 UTC
Creator9BvPQTeipmg7UZvBtknQkadPdgZ5ekyWVPg1LrSbTYP8
Creator took26.6% 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: 5 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 fromiqPukmzra3p9aUDN66bhTB… slot 467,980,476
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-11 03:57:21 UTC
Slot 467,980,476, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in5 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-11-11 03:58:07 UTC +46s
9.816e-8 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 19 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 1,007 launches from 712 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 creator39 earlier launches. All 3 that reached the graduation threshold on our feed were read on chain, and none had completed. 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 3 other creator wallets, across 6 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
NameCate
Metadata heldsha256 171c5d7cfb399f47c8f6eee8084a3f0b23e70822b356cb71529a9ec6e46b05a0 · 289 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 10a1c4b66101708779145447bc7b1bc3f9f44b65ea423ffc5d45b20c61709403 · 85,278 bytes

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