1,400,708 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

STONKRUSH

The creator took 48% of supply at 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 2 other launches from 3 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, 45.8% 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.

8BRRKNKnW8AhenTtQqpEcpYv26kVPunRjJubK8JXSTNK 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 48.2% of supply at launch.

At launch

Created2026-10-04 16:25 UTC
CreatorG4pHrKZFCWERVNaF2e1ebacSgzudjYLs2QwiRAun6Rxu
Creator took48.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.
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 recorded - this venue's trades do not name the wallet
Recorded from4CytUWLYpbaBdS7FewhoZW… slot 453,309,600
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-04 16:25:01 UTC
Slot 453,309,600, which is the chain's own clock for this moment.
Highest price seen2026-10-04 16:25:01 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.

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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 5 launches from 5 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 →
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 of 3 creator wallets in all. 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
NameStonk Rush
Metadata heldsha256 f509376ffd02eceeefc0651fabb0a9c8d342fcd29d1b4c3737bfe2916e7806fa · 230 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 c181d9365bd372e422dffece2a22526bc6c7923fa05f3bc065aa652bfcbea92a · 26,659 bytes

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