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

WILDWOOD

The curve completed 15s 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 63 other launches from 39 creator wallets in all, and this creator has 522 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, 53.2% 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.

CrSCphSin4iVXFwKT7JKBTGUh8M7PTp9fsivKoREpump Solscan pump.fun

Cite this record as: Chain of Title, WILDWOOD (The anti-AI Movie), mint CrSCphSin4iVXFwKT7JKBTGUh8M7PTp9fsivKoREpump, observed at creation 2026-10-24 21:54 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/CrSCphSin4iVXFwKT7JKBTGUh8M7PTp9fsivKoREpump

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 15s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-10-24 21:54 UTC
Creator4Lm2uqHgauVS1gzzNCd1F4FeGNwzUp6dXp5uqHxmrnDX
Creator took12.6% of supply in the first block
Outside buyers25 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: 25 within the first 30s, 0 in the very same block the token was created in.
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 soldyes
Recorded from38CLU1RBYUsVPmZtRLJWgp… slot 461,010,341
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-10-24 21:54:12 UTC
Slot 461,010,341, 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-24 21:54:27 UTC +15s
Confirmed against the venue's own completion state.
Thirty seconds in25 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 64 launches from 39 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 53.2% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 157 launches from 78 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.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 other launches, across 4 creator wallets in all. Across the archive, 30.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator522 earlier launches, 12 confirmed complete on chain, 2 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 403 other creator wallets, across 501 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, 60.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

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
NameThe anti-AI Movie
Metadata heldsha256 275b7cb071e73ef8f9b626a0eae4a66a84b2210aa8a24dc491300fb9f7503dc4 · 481 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 1aa62d4f0b847d75e46fc37801f3e45a9f07730942673db624939d95be0d395e · 14,326 bytes

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