3,548,044 launches on record
Coverage from 2 Sep 2026
Archive read 12 Nov 2026
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-12 14:11 UTC

BROKECAT

Broke Cat

FGtbZ9ui168X4HWdhTgzUoVHWVe19CwtUvZgvLRSpump Solscan pump.fun
3.4%of supply taken by the creator in the first block
407outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
90launches carry this ticker, from 81 creator wallets
1other launch declared this same launch document, byte for byte
8other launches used this exact picture file
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 8 other launches from 9 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.3% 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.

noteThe creator sold while we were watching.
noteOnly 0.9 SOL of liquidity was in the pool just now.

At launch

Created2026-11-12 14:11 UTC
Creator8dVqkghjLuCcQC7egJfm9VeGMiEkNnnZfCnYetcz4xaR
Creator took3.4% of supply in the first block
Outside buyers407 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: 73 within the first 30s, 10 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.
Graduated5 min after launch
Curve on chainComplete. We read the bonding curve account 12.0 h ago and it was finished. Checked 2026-11-12 14:30 UTC.
Creator soldyes
Recorded fromQf4AvRMVHMsmQ37Vz89E5w… slot 468,553,988
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-12 14:11:14 UTC
Slot 468,553,988, which is the chain's own clock for this moment.
Creation block10 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in73 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.
Curve completed2026-11-12 14:16:15 UTC +5m 01s
Confirmed against the venue's own completion state.

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 9 launches from 9 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 90 launches from 81 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 1 other launch, across 2 creator wallets in all. Across the archive, 33.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

Pool

Liquidity0.9 SOL
Read from chain2026-11-13 02:28 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameBroke Cat
Metadata heldsha256 883ab72d2dd48d55c85be069b3ef7ab561f7f7270b2a2a1f2e5a30f6a82be9d3 · 362 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 577403be5ab7d424e4f4fa8e1c4ed7ce2c46ffe61b551c3862b722f05e5abf68 · 2,182 bytes

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