1,517,287 launches on record
Coverage from 2 Sep 2026
Archive read 09:49 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

TARD

The curve completed 39s 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 6 other launches from 7 creator wallets in all, and this creator has 1,077 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.7% 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.

941BtBo8qDbuo33H4kYqK7YvsFEJ4gHhEuHM3JJTkcR8 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.
noteThe creator took 20.1% of supply at launch.
findingIt left the curve 39s after launch.

At launch

Created2026-10-06 16:24 UTC
Creator5FqUo9aBjsp7QeeyN6Vi2ZmF2fjS4H5EU7wnAQwPy17z
Creator took20.1% 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.
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 soldnot recorded - this venue's trades do not name the wallet
Recorded from5abvN5bpwbfZWwp4jkt8JY… slot 453,954,387
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 16:24:34 UTC
Slot 453,954,387, which is the chain's own clock for this moment.
Highest price seen2026-10-06 16:24:34 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 16:25:13 UTC +39s
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 7 launches from 7 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 46.7% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 93 launches from 71 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.4% 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.5% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator1,077 earlier launches, 35 confirmed complete on chain, 9 with findings on record. Across the archive, 71.5% 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 599 other creator wallets, across 1,459 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.9% 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
NameTesla Assisted Regulated Driving
Metadata heldsha256 0ba52612386c4953472b4d2687f4e34348e7e04f09e8b1157ce65bad8989233f · 347 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 966de8c7879e0a13e5e1d2d5babe7d3e9d0ac8d5efb18d10feec2ffd121403f2 · 24,267 bytes

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