3,104,576 launches on record
Coverage from 2 Sep 2026
Archive read 3 Nov 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

sol

Only 1 outside buyer bought its curveRead 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 3,920 other launches from 1,146 creator wallets in all, and this creator has 7 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, 55% 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.

8NxZYtSSAMutTBcDqDELGrNrw9t4QRK8VoahbEAUpump Solscan pump.fun

Cite this record as: Chain of Title, sol (goku coin), mint 8NxZYtSSAMutTBcDqDELGrNrw9t4QRK8VoahbEAUpump, observed at creation 2026-11-03 19:22 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/8NxZYtSSAMutTBcDqDELGrNrw9t4QRK8VoahbEAUpump

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.

findingOnly 1 outside buyer bought on the bonding curve before it graduated.

At launch

Created2026-11-03 19:22 UTC
CreatorDi9QnG6g4sp1Qtznd6XWeGXGjJyJqxiamC72JnDpVh9F
Creator took0.3% of supply in the first block
Outside buyers1 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: 1 within the first 30s, 0 in the very same block the token was created in.
Graduated3 min after launch
Curve on chainComplete. We read the bonding curve account 2.9 h ago and it was finished. Checked 2026-11-03 23:12 UTC.
Creator soldnot while we watched
Recorded from2uZKfjG8nW8t9LA42KGryx… slot 465,014,655
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-03 19:22:27 UTC
Slot 465,014,655, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in1 distinct buyer, 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-11-03 19:25:20 UTC +2m 53s
Confirmed against the venue's own completion state.
Highest price seen2026-11-03 19:25:20 UTC +2m 53s
1.090e-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 pictureOn 3,919 launches from 1,146 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 12,220 launches from 4,406 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.2% 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,777 other launches, across 1,134 creator wallets in all. Across the archive, 31.8% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator7 earlier launches, 1 confirmed complete on chain. Across the archive, 70.5% 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
Namegoku coin
Metadata heldsha256 5b3bd375be5537d6b751e1882c7a1bdd64698891ce636b02823826ee527fa68e · 177 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 3d1fc6383cbce3a58ec495b52e179368488d5a391d1e86c5d6f24a31757646ed · 469,431 bytes

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