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

SSSX

The curve completed 58s 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 creator has 6 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.

5JTjcX8fBzwew4q3Nq4eJHevSZ9cxHRHk7SFPmgopump Solscan pump.fun

Cite this record as: Chain of Title, SSSX (Spooky Scary Skeletons), mint 5JTjcX8fBzwew4q3Nq4eJHevSZ9cxHRHk7SFPmgopump, observed at creation 2026-10-25 23:48 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/5JTjcX8fBzwew4q3Nq4eJHevSZ9cxHRHk7SFPmgopump

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

At launch

Created2026-10-25 23:48 UTC
Creator9jKyNy4ezS2evzzqMgWUanC6x9FhsQjuSZP1cx2kK2g6
Creator took0.2% of supply in the first block
Outside buyers10 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.
Graduated1 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 from2iZxT4kNN2gtf8VbF7PBnt… slot 461,449,491
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-25 23:48:30 UTC
Slot 461,449,491, 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-10-25 23:49:28 UTC +58s
Confirmed against the venue's own completion state.

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 creator6 earlier launches. Across the archive, 70.2% 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
NameSpooky Scary Skeletons
Metadata heldsha256 e2806eb7823cfbdc7dfb011f6987f5bca0423764cd91ecf938ca4ad4e67552dd · 204 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 bb2264070b07e0547e8f880380502c100fe5d0677549e84d535e6caba36cccd5 · 21,415 bytes

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