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

GWC

The curve completed 28s 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 creator has 1,200 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. 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.

8UoCVd6AUSANE1siaHm69oiDKvK5xTSb8cMKJc1Cm9W1 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 28s after launch.

At launch

Created2026-10-03 22:45 UTC
CreatorE4FPggw9yDp9PNJDuRoLYDr6a5HKCsAterw3fygLpZEA
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.
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 from3EUcBVwcNqvWs1UtZKLzaq… slot 453,071,753
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-03 22:45:38 UTC
Slot 453,071,753, which is the chain's own clock for this moment.
Curve completed2026-10-03 22:46:06 UTC +28s
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 63 launches from 48 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 creator1,200 earlier launches, 68 confirmed complete on chain, 2 with findings on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 389 other creator wallets, across 743 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
NameGiant Wiener Chatbot
Description-
Metadata heldsha256 ed10ecc7f23c95dc8faa84475923160d7938d42748d821949293ef078bfff9d9 · 322 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 d7243a7cccf665f8f8ce8cb0510f7ef75305da630c6b2267a4aeb16f067f1151 · 195,562 bytes

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