2,613,462 launches on record
Coverage from 2 Sep 2026
Archive read 02:56 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

REAPURR

The curve completed 9s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

21VTKjxBfUV5jVR9AbcoPvGqRmFRejvhczbjaLiTmd77 Solscan

Cite this record as: Chain of Title, REAPURR, mint 21VTKjxBfUV5jVR9AbcoPvGqRmFRejvhczbjaLiTmd77, observed at creation 2026-10-27 21:33 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/21VTKjxBfUV5jVR9AbcoPvGqRmFRejvhczbjaLiTmd77

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.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
findingIt left the curve 9s after launch.

At launch

Created2026-10-27 21:33 UTC
Creator4CBSwxSRnjU4KjR9XyM9yaMaoMfX4Zv4j6xfaey4Xtfj
Creator took5.2% 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.
Graduated0 min after launch
Curve on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot recorded - this venue's trades do not name the wallet
Recorded fromR4Bsbx1C6Jy6JgY5uRLAGL… slot 462,224,044
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
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.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-27 21:33:16 UTC
Slot 462,224,044, which is the chain's own clock for this moment.
Highest price seen2026-10-27 21:33:16 UTC
2.796e-8 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.
Curve completed2026-10-27 21:33:25 UTC +9s
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 18 launches from 18 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, 88.4% 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
NameREAPURR
DescriptionThe reapurr keeps the book of the dead. Every coin has its day; he keeps the record. Holders earn SOL reflections from every trade, and every night he reaps more on top: hold through his checks, play his games, get paid.
Metadata heldsha256 7b456b057d6f273f11841d0765961469ea499c8ddaaa5e77e0b3d2f8ebaa12f4 · 448 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 c55503f32fa3db01cc5521069e4aa8424fcbcfc5ea3b8bef25422c36d2a4eb92 · 258,897 bytes

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