2,941,358 launches on record
Coverage from 2 Sep 2026
Archive read 17:27 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

ROYALE

Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 12.5%, 442 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this picture is on 2 other launches, and this creator has 9 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.

8e7rkycmmQLyAvULWA3x37N18RHo1kdQSTpPxnuhpump Solscan pump.fun

Cite this record as: Chain of Title, ROYALE (Meme Royale), mint 8e7rkycmmQLyAvULWA3x37N18RHo1kdQSTpPxnuhpump, observed at creation 2026-10-31 17:23 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/8e7rkycmmQLyAvULWA3x37N18RHo1kdQSTpPxnuhpump

At launch

Created2026-10-31 17:23 UTC
Creator8VujHGHzNXcV5yGUvCZwgxEAdFHKfttYbKHqNTxUBZoj
Creator took12.5% of supply in the first block
Outside buyers442 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: 69 within the first 30s, 0 in the very same block the token was created in.
Graduated10 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 soldnot while we watched
Recorded from3d2RSbf4ZFiT97yjG6FMBv… slot 463,771,310
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-10-31 17:23:48 UTC
Slot 463,771,310, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in69 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.
Curve completed2026-10-31 17:34:06 UTC +10m 18s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-31 17:34:06 UTC +10m 18s
4.109e-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 tickerOn 42 launches from 38 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 →
This creator8 earlier launches, 2 confirmed complete on chain, 1 with findings on record. Across the archive, 70.1% 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 9 other creator wallets, across 8 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, 62.1% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity49.0 SOL
Read from chain2026-10-31 20:11 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameMeme Royale
DescriptionThe playable economy of Meme Royale. Build your deck, deploy your favourite meme characters, defend your towers and battle other players in real time. Created on Imagine.
Metadata heldsha256 191f3316f793f3d560d1a83f83b90d2c2d1deb61042b9a48278bfecb1ad451d6 · 588 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 3c876e27f1fe58483c218bfb33738d2a04ae0b883d456ed1a53bceaf379d3741 · 116,683 bytes

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