1,846,529 launches on record
Coverage from 2 Sep 2026
Archive read 13 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

TOOT

The curve completed 48s 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 creator has 23 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.

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.

7ZAbrAFuS1VxsfXixbqhV3toobU4dXhjEMz1R7SWpump Solscan pump.fun

Cite this record as: Chain of Title, TOOT, mint 7ZAbrAFuS1VxsfXixbqhV3toobU4dXhjEMz1R7SWpump, observed at creation 2026-09-03 16:12 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/7ZAbrAFuS1VxsfXixbqhV3toobU4dXhjEMz1R7SWpump

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 48s after launch.
noteThe creator sold while we were watching.
noteOnly 0.1 SOL of liquidity was in the pool just now.

At launch

Created2026-09-03 16:12 UTC
Creator51Bybg8iBqtwr36sMdK4t1o86fNFb7YK5G57vDbhWsxw
Creator took4.3% of supply in the first block
Outside buyersunknown 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: 2 within the first 30s, 0 in the very same block the token was created in.
Graduated1 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 soldyes
Recorded fromEDcoQ1hwSp2xqL8s5AEGMB… slot 444,013,948
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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.

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-09-03 16:12:55 UTC
Slot 444,013,948, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in2 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-09-03 16:13:43 UTC +48s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-03 16:15:07 UTC +2m 12s
2.228e-7 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 14 launches from 14 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 →
This creator23 earlier launches. All 1 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity0.1 SOL
Read from chain2026-10-14 01:37 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameTOOT
DescriptionHe doesn’t roar. He doesn’t bark. He TOOTS! 🐘
Metadata heldsha256 df92b69b88951ba99cbb6d2e59d83da1eda3b381ef9c53601809ef3088de6476
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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-22 17:24 UTC.
Picture heldsha256 ea7993a0d9f7e2ff2eed588901acd11c4dc47761dbdd6aa412b1c65c4beec5bd · 1,122,573 bytes

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