2,355,618 launches on record
Coverage from 2 Sep 2026
Archive read 24 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

KR

The curve completed 23s 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 16 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.

2NgrdiLy5EJm6rhbFx5cahXbYVi4Sp2rgwQnWUSwpump Solscan pump.fun

Cite this record as: Chain of Title, KR (Ronaldo), mint 2NgrdiLy5EJm6rhbFx5cahXbYVi4Sp2rgwQnWUSwpump, observed at creation 2026-10-24 12:22 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/2NgrdiLy5EJm6rhbFx5cahXbYVi4Sp2rgwQnWUSwpump

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 23s after launch.

At launch

Created2026-10-24 12:22 UTC
Creator7HH3mrQx2NHQaQfCkdRqDFpAwsqaCiF6ZhqS1dTVS2VA
Creator took0.2% of supply in the first block
Outside buyers16 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: 6 within the first 30s, 0 in the very same block the token was created in.
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 while we watched
Recorded from3dZkcE53byRyt6NPnLTfeG… slot 460,848,746
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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-24 12:22:48 UTC
Slot 460,848,746, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-24 12:23:11 UTC +23s
Confirmed against the venue's own completion state.
Thirty seconds in6 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.

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 17 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.2% wear one that more than one creator wallet has launched. See this ticker's page →
This creator16 earlier launches. All 3 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70.1% 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
NameRonaldo
Metadata heldsha256 a95735759c3ac6954e9e6af5b481fc10a4a4807872338d8de09afe8f68977e70 · 187 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 3d6a18adde29f6350282656b3e09d14eedce053792202e43b96889f46c1c7819 · 1,455,204 bytes

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