2,376,848 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

experience

The curve completed in the same batch of events as the 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 1 other launch from 2 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.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.

5b8Jjs2yUcWN6kqoVewA9d8hybo1TVL8YUBe7Dnbpump Solscan pump.fun

Cite this record as: Chain of Title, experience, mint 5b8Jjs2yUcWN6kqoVewA9d8hybo1TVL8YUBe7Dnbpump, observed at creation 2026-10-25 14:36 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/5b8Jjs2yUcWN6kqoVewA9d8hybo1TVL8YUBe7Dnbpump

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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 9 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 3.1 SOL of liquidity was in the pool just now.

At launch

Created2026-10-25 14:36 UTC
Creator4cLmpmKTUnZKNinYDuZQQmELNeT9m9AYKVt3fFuKwRGJ
Creator took3.4% of supply in the first block
Outside buyers9 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 re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldno
Recorded from4D6fbPxPGFPHovzS4rnFS8… slot 461,293,394
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.

Order of events

Created2026-10-25 14:36:03 UTC
Slot 461,293,394, which is the chain's own clock for this moment.
Creation block8 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-25 14:36:03 UTC +0s
Confirmed: a PumpSwap pool was found for it.
Thirty seconds in9 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 2 launches from 2 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 11 launches from 10 creator wallets. 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 1 other launch, across 2 creator wallets in all. Across the archive, 30.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

Pool

Liquidity3.1 SOL
Read from chain2026-10-26 01:35 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Nameexperience
Metadata heldsha256 c0ebe6dfa2ae1815ec42caad533b890c2d9d9a5646222c05759290fb302f43ef · 320 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 5d413f7d7393907dd9fbd22365f82de6e5055b139432709a36a7ce821a38d608 · 99,802 bytes

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