3,461,686 launches on record
Coverage from 2 Sep 2026
Archive read 03:18 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

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.

GKL9iaqj5qAXL4jwv2DAbtd41NGPTFtxGGPCAjynpump Solscan pump.fun

Cite this record as: Chain of Title, (Anthropic), mint GKL9iaqj5qAXL4jwv2DAbtd41NGPTFtxGGPCAjynpump, observed at creation 2026-11-11 01:45 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/GKL9iaqj5qAXL4jwv2DAbtd41NGPTFtxGGPCAjynpump

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.

noteThe creator sold while we were watching.

At launch

Created2026-11-11 01:45 UTC
Creator3U2Sj72KgrMoD8y6mzutC7ro5pS1XueyssX5VxoJ4DEG
Creator took0.0% of supply in the first block
Outside buyers0 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: 0 within the first 30s, 0 in the very same block the token was created in.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldyes
Recorded from4gRbW5ozNLaD9v7XKeoGZF… slot 467,943,723
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_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-11-11 01:45:53 UTC
Slot 467,943,723, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds inNo 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.

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 pictureNo other launch we hold a picture for used this one.

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
NameAnthropic
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 6eebbe0673c4277a33ecc015f744741320fd8baa5edd9d7eef553031c77ddbf2 · 253 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 751ba510cad0f3ee90a4fe5f516246ea6e90de07e2633588a2ca82eb25eb548b · 9,969 bytes

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