1,837,644 launches on record
Coverage from 2 Sep 2026
Archive read 07:07 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

SC

Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 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, 48.9% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

4J9KAqH7qTx7EJYzEV1K36yLn4ruowN9sFkPEdGSpump Solscan pump.fun

Cite this record as: Chain of Title, SC (Slopcats), mint 4J9KAqH7qTx7EJYzEV1K36yLn4ruowN9sFkPEdGSpump, observed at creation 2026-10-11 22:25 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/4J9KAqH7qTx7EJYzEV1K36yLn4ruowN9sFkPEdGSpump

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.

noteOnly 2.1 SOL of liquidity was in the pool just now.

At launch

Created2026-10-11 22:25 UTC
CreatorbvM52VKjJ6CWZbsjFV9zBE9rXEtJDndQ1d2vfMHk8kX
Creator took0.8% of supply in the first block
Outside buyers398 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: 51 within the first 30s, 0 in the very same block the token was created in.
Graduated8 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from4vM75rEyGtnxqVzyLBcqWi… slot 455,814,956
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-10-11 22:25:21 UTC
Slot 455,814,956, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in51 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-10-11 22:33:18 UTC +7m 57s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-11 22:44:55 UTC +19m 34s
9.158e-7 SOL per token. Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a decoded one. 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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 48.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 697 launches from 502 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, 87.2% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity2.1 SOL
Read from chain2026-10-13 10:13 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameSlopcats
Metadata heldsha256 d58b104d1f4c16af7c951aa050ad81006d2a79a53a88b1baf1d2a0356b953e09 · 250 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 85f49879c91a42b8c4c6c103f3cbea704e8d2e83bee66a36f907ffc4d3d16fe5 · 143,481 bytes

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