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

YqwbW9hr

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 1 other launch, all of them this same creator's. 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.5% 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.

5cS2E5La7VkGrJAsLGUEjDRF1BsJPhdcLq5A3MqDpump Solscan pump.fun

Cite this record as: Chain of Title, YqwbW9hr (The 4Chan Quant), mint 5cS2E5La7VkGrJAsLGUEjDRF1BsJPhdcLq5A3MqDpump, observed at creation 2026-10-12 10:57 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/5cS2E5La7VkGrJAsLGUEjDRF1BsJPhdcLq5A3MqDpump

At launch

Created2026-10-12 10:57 UTC
CreatorA8HERF7kTijvYcQt6W3nhSTFmdCE9VSJK7Cti5nCGGdR
Creator took9.4% of supply in the first block
Outside buyers810 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: 159 within the first 30s, 8 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.
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 soldnot while we watched
Recorded from5i95Jm8Fi7oHpFY3A4itiU… slot 456,021,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-12 10:57:58 UTC
Slot 456,021,956, which is the chain's own clock for this moment.
Creation block8 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in159 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-10-12 10:59:08 UTC +1m 10s
2.969e-7 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 21 launches from 13 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.1% wear one that more than one creator wallet has launched. See this ticker's page →

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
NameThe 4Chan Quant
DescriptionCreated on https://rapidlaunch.io
Metadata heldsha256 2caaf50159cf54ce8284dd32ef024e5dcaf19d5fd2256fbd907f79ab90c2bbcc · 274 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 2d30b803ee7179710ec5681128aad82823d4192e31a6f882d55fe60d3d0fba9a · 2,843 bytes

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