1,833,098 launches on record
Coverage from 2 Sep 2026
Archive read 04:07 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

KACY

The curve completed 17s 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 19 other launches from 20 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, 48.9% 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.

54zFTXkZGLK85mBPeNSaYFLbGSvAr5RMxatFFe3Ppump Solscan pump.fun

Cite this record as: Chain of Title, KACY (Mark Kacy), mint 54zFTXkZGLK85mBPeNSaYFLbGSvAr5RMxatFFe3Ppump, observed at creation 2026-10-12 18:22 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/54zFTXkZGLK85mBPeNSaYFLbGSvAr5RMxatFFe3Ppump

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 17s after launch.

At launch

Created2026-10-12 18:22 UTC
Creator9FYHry7aeZXS7kmxvjVXvyMcq3JHMyazbRyBW121pwi4
Creator took10.0% of supply in the first block
Outside buyers181 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: 181 within the first 30s, 10 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 13.4 h ago and it was finished. Checked 2026-10-12 18:51 UTC.
Creator soldnot while we watched
Recorded frommHa6pKJwFhE7gWw5oceWHo… slot 456,143,637
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-12 18:22:29 UTC
Slot 456,143,637, which is the chain's own clock for this moment.
Creation block10 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-12 18:22:45 UTC +17s
Confirmed against the venue's own completion state.
Highest price seen2026-10-12 18:22:45 UTC +17s
4.109e-7 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.
Thirty seconds in181 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 20 launches from 20 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 48.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 24 launches from 24 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.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 17 other launches, across 18 creator wallets in all. Across the archive, 25.7% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 17 other creator wallets, 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 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, 58.3% 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
NameMark Kacy
DescriptionLazy animations, from me to you.
Metadata heldsha256 a0c495a514e2a1e0e76ee26c2bdd123e4a8d6e76d56fff929572fad7e5ec1876 · 298 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 069194bcc6b0e5663de17f2491012104eb7c2b0c81cc7a025a48a71e3ea249f0 · 27,363 bytes

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