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

moocat

Only 7 outside buyers bought its curveRead 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 28 other launches, all of them this same creator's, and this creator has 50 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, 14.7% of the launches whose picture we hold carry one only their own creator reused. 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.

5W3CUwb1ZvShABTTYJi8XGnQhZdHgvHcRFP5Brfupump Solscan pump.fun

Cite this record as: Chain of Title, moocat (moon cat), mint 5W3CUwb1ZvShABTTYJi8XGnQhZdHgvHcRFP5Brfupump, observed at creation 2026-10-10 02:43 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/5W3CUwb1ZvShABTTYJi8XGnQhZdHgvHcRFP5Brfupump

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.

findingOnly 7 outside buyers bought on the bonding curve before it graduated.
noteThe creator sold while we were watching.

At launch

Created2026-10-10 02:43 UTC
Creator6gERpWNKQnta98NW1et2im3LxGMmihByrz1aShZBhz2T
Creator took0.2% of supply in the first block
Outside buyers7 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: 3 within the first 30s, 1 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.
Graduated4.3 h after launch
Curve on chainComplete. We read the bonding curve account 11.3 h ago and it was finished. Checked 2026-10-10 08:47 UTC.
Creator soldyes
Recorded from2ZwmnQpEzwhFKW97DNjKJu… slot 455,094,456
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-10 02:43:34 UTC
Slot 455,094,456, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in3 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-10 06:59:29 UTC +4h 15m 55s
Confirmed against the venue's own completion state.
Highest price seen2026-10-10 07:03:55 UTC +4h 20m 21s
1.215e-6 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 29 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.7% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 7 launches from 5 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, 86.9% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 2 other launches, all of them this same creator's. Across the archive, 11.2% of the launches whose document we hold carry one only their own creator reused. See them →
This creator50 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 →

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
Namemoon cat
Metadata heldsha256 1f0dc38a278a5602e3195c7b3195583cb7cde6a325e0ea1c8934af5cc50ecb73 · 192 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 26aa2fe42216f30da3f462ae623a144d809471d6c759b5ea03a24259c8c42fe2 · 5,870 bytes

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