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

rolex

The curve completed 10s 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 4 other launches, all of them this same creator's, and this creator has 176 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, 14.3% 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.

v7WnLDvgpfrv9ud28tydGr4dNXNJwWVomgkM513pump Solscan pump.fun

Cite this record as: Chain of Title, rolex (rolex screenshot), mint v7WnLDvgpfrv9ud28tydGr4dNXNJwWVomgkM513pump, observed at creation 2026-10-14 12:10 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/v7WnLDvgpfrv9ud28tydGr4dNXNJwWVomgkM513pump

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

At launch

Created2026-10-14 12:10 UTC
Creator51NkBNc7RVwXLv7C6rivNcENrnEfFg3LiWDXeyCX4hRL
Creator took0.3% of supply in the first block
Outside buyers21 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 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 from51ANQFnr1j58ZGGZxu6akN… slot 456,833,519
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-14 12:10:32 UTC
Slot 456,833,519, 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-14 12:10:42 UTC +10s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-14 12:10:42 UTC +10s
1.305e-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 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 pictureOn 5 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.3% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 130 launches from 112 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.4% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 4 other launches, all of them this same creator's. Across the archive, 11.2% of the launches whose document we hold carry one only their own creator reused. See them →
This creator176 earlier launches. All 28 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 69.9% 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-15 11:58 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Namerolex screenshot
Descriptionscreenshot of a rolex just 22k’s i am not saying what you need to do, but don’t sleep if this one is the one
Metadata heldsha256 a9e9d437845e1e7bd31cd381f516293cc3c50ec85c7b623ca4dea7ecccf51bf7 · 312 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 d77b442406c286bfe8ed2ae9e4158812af434ba2779baeb3d0a8d3e1453ad626 · 798,078 bytes

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