1,343,975 launches on record
Coverage from 2 Sep 2026
Archive read 12:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

Aiden

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 10 other launches from 3 creator wallets in all, and this creator has 5 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, 45.3% 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.

46GJpDyxTxyPN5wsz1FZetD1yXWyGM3eCG5mpfYUdwCk 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.

At launch

Created2026-10-04 01:35 UTC
CreatorAiYaDeeVL4F8i8ovpJa3g9CJocUsMRZca9jA2swdfFSw
Creator took0.0% 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.
Graduated4 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 from2s1DBMuF3n1gDHDsgpfXYb… slot 453,109,958
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. peak_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.

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-04 01:35:52 UTC
Slot 453,109,958, which is the chain's own clock for this moment.
Curve completed2026-10-04 01:40:09 UTC +4m 17s
Confirmed against the venue's own completion state.

Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.

Seen before

This pictureOn 11 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 450 launches from 293 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. See this ticker's page →
This documentThe same launch document, byte for byte, as 10 other launches, across 3 creator wallets in all. See them →
This creator5 earlier launches, 4 confirmed complete on chain. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 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. 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
NameThe Day Trader
Metadata heldsha256 46496f8ee1779b071d806d7d47db0a409a08d1b9d15d2cba1dd55a86e07ca07b · 493 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 fbdf7cec12bb38a6c7ed20a0838773aae0a75671af46a5f14a900621cd78ac18 · 2,967 bytes

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