1,902,056 launches on record
Coverage from 2 Sep 2026
Archive read 16:06 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

SEALS

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.

Also recorded, and not part of the finding above: this picture is on 5 other launches, all of them this same creator's, and this creator has 22 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, 14.3% of the launches whose picture we hold carry one only their own creator reused. 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.

Bx8tdtxs7SCrPK9Wwj6eDowBeNn3npUey4fsmZafpump Solscan pump.fun

Cite this record as: Chain of Title, SEALS (SAVE THE SEALS), mint Bx8tdtxs7SCrPK9Wwj6eDowBeNn3npUey4fsmZafpump, observed at creation 2026-10-14 06:56 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Bx8tdtxs7SCrPK9Wwj6eDowBeNn3npUey4fsmZafpump

At launch

Created2026-10-14 06:56 UTC
CreatorFeScffHivvRD4oug3t8AGJVrJrUWAirrZiQrfi3J5SsG
Creator took0.2% 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 soldnot while we watched
Recorded from2uZNmUxSuJoNX4S32wcAUZ… slot 456,746,472
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.

Order of events

Created2026-10-14 06:56:00 UTC
Slot 456,746,472, 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.
Highest price seen2026-10-14 06:58:28 UTC +2m 28s
2.911e-8 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 6 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.3% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 255 launches from 181 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, 87.3% wear one that more than one creator wallet has launched. See this ticker's page →
This creator21 earlier launches. All 1 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 69.9% 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 1 other creator wallet, across 2 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 of 2 creator wallets in all. Across the archive, 58.5% 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
NameSAVE THE SEALS
DescriptionSaving seals is critical because they are apex predators that maintain the balance and health of our marine ecosystems. Without seals, the delicate oceanic food web could collapse, leading to a dangerous overpopulation of prey species and a decline in larger marine predators. SAVE THE SEALS.
Metadata heldsha256 b8892b5b4afcca015fad58e948790d08ff0207d60a13f751d63fd9042d012aa0 · 939 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 3f6f7701a6d4ca2321f429bd56320b2ad37d3c3007bd47e2fc414878e13bb276 · 444,459 bytes

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