3,089,297 launches on record
Coverage from 2 Sep 2026
Archive read 16:48 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

🚀

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 picture is on 330 other launches from 2 creator wallets in all, and this creator has 8,084 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, 54.9% of the launches whose picture we hold carry one a different creator also used. 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.

GVccXami3xxmnHP1P2M59nTSygLUHKNNZSHuwEThpump Solscan pump.fun

Cite this record as: Chain of Title, 🚀, mint GVccXami3xxmnHP1P2M59nTSygLUHKNNZSHuwEThpump, observed at creation 2026-11-02 15:40 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/GVccXami3xxmnHP1P2M59nTSygLUHKNNZSHuwEThpump

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

At launch

Created2026-11-02 15:40 UTC
Creator7FVfSdnR9VPGjMtmBP1Hz9C2DFTpoNX8gVVRmnimnGt9
Creator took0.4% of supply in the first block
Outside buyers15 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: 7 within the first 30s, 0 in the very same block the token was created in.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 1.2 days ago and it was finished. Checked 2026-11-02 15:43 UTC.
Creator soldyes
Recorded from4VNSmwqYKu7QRRjLwnanNS… slot 464,549,115
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.

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-11-02 15:40:39 UTC
Slot 464,549,115, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-11-02 15:41:02 UTC +23s
Confirmed against the venue's own completion state.
Highest price seen2026-11-02 15:41:02 UTC +23s
1.501e-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.
Thirty seconds in7 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 pictureOn 331 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 54.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 636 launches from 135 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, 89.1% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 278 other launches, across 2 creator wallets in all. Across the archive, 31.7% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator8,031 earlier launches, 75 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 →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 43 other creator wallets, across 88 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.6% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity0.0 SOL
Read from chain2026-11-03 19:58 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Name🚀
Descriptionto the moon
Metadata heldsha256 0dec636ce6890dc894ede5bb88e5c06ef7a127fc9d3fc12053b4813c894194bc · 197 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-11-03 15:42 UTC.
Picture heldsha256 6207d0fe615ee772a3360b3d665e0b07347d89067399b84e244f95d1c8f4ca8b · 72,859 bytes

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