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

DICTATOR

The curve completed 1s 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 34 other launches from 25 creator wallets in all. 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, 53.8% 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.

Fr65rEiYDa7c6iAxj8Yijx8q4yMyg4UEP7VfsakwwupS Solscan

Cite this record as: Chain of Title, DICTATOR (Mbappe Zedong), mint Fr65rEiYDa7c6iAxj8Yijx8q4yMyg4UEP7VfsakwwupS, observed at creation 2026-10-27 11:10 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Fr65rEiYDa7c6iAxj8Yijx8q4yMyg4UEP7VfsakwwupS

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

At launch

Created2026-10-27 11:10 UTC
CreatorCZ9xdDCk8LRybSYUNM4Wf5ZTi4MmRYJCAE1gVUThjLCm
Creator took0.0% 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 from4WqtVyWN4CCnybW8PbxPWC… slot 462,048,636
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. peak_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-27 11:10:46 UTC
Slot 462,048,636, which is the chain's own clock for this moment.
Curve completed2026-10-27 11:10:47 UTC +1s
Confirmed against the venue's own completion state.

Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.

Seen before

This pictureOn 35 launches from 25 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 53.8% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 126 launches from 89 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.3% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 3 other launches, across 4 creator wallets in all. Across the archive, 30.8% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

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
NameMbappe Zedong
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 b29e78979a22e2087fbc2cff0a654bd2b9490f6f238258ab422ac000db8733c4 · 465 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 36ec7b70fba3dd1913d199835d55d9e4ae1e64c651186bfd2ef0c984cdef8956 · 3,794 bytes

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