1,476,445 launches on record
Coverage from 2 Sep 2026
Archive read 18:27 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

vCat

The curve completed 1s 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 3 other launches from 4 creator wallets in all, and this creator has 1,612 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, 46.4% 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.

Fk7527rwQSiaN1tS6XN72u3FNNW4WxZTWcuBapGz8YbD Solscan

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.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
findingIt left the curve 1s after launch.

At launch

Created2026-10-06 15:24 UTC
Creator8ZN71XTdVo8yRovnGLmNgW3Tgniw6A4J3JGLvPD686FP
Creator took12.2% of supply in the first block
Outside buyersunknown 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 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 soldnot recorded - this venue's trades do not name the wallet
Recorded from57fGJg8zrYf9EmZgHiajtL… slot 453,941,028
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
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.

Order of events

Created2026-10-06 15:24:21 UTC
Slot 453,941,028, which is the chain's own clock for this moment.
Highest price seen2026-10-06 15:24:21 UTC
0.000e+0 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.
Curve completed2026-10-06 15:24:23 UTC +1s
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 pictureOn 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 46.4% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 95 launches from 72 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, 86.3% 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, 23.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator1,612 earlier launches, 46 confirmed complete on chain, 12 with findings on record. Across the archive, 71.7% 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 852 other creator wallets, across 2,220 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, 57.8% 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
NameVenice Cat
Metadata heldsha256 f47cafce5f5b9c91b15612fce6a08a92da86c0c8a738e9073b6fb0735c9a7f23 · 308 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 fd5adb1516e2a830c96d5f3b5f4a749cd733af376f30f8295ea8021ff6a72ed5 · 15,714 bytes

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