3,514,061 launches on record
Coverage from 2 Sep 2026
Archive read 06:31 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Launch record · observed at creation 2026-10-05 20:46 UTC

LFG

LFG Cooking

4etDBYBetve3dQTbxUM7QcFzt9MssxmJQS9XzWStgALf Solscan
78.0%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
179launches carry this ticker, from 119 creator wallets
The creator took 78% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.
findingThe creator took 78.0% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
findingIt left the curve 1s after launch.

At launch

Created2026-10-05 20:46 UTC
CreatordgVCiUjyeEJuMzmZbo3ZBmi52ETpQHfuyR2sGimHRHL
Creator took78.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 fromza8JYUX42p5jeu7GQhih29… slot 453,690,482
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.

Order of events

Created2026-10-05 20:46:22 UTC
Slot 453,690,482, which is the chain's own clock for this moment.
Highest price seen2026-10-05 20:46:22 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-05 20:46: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 tickerOn 179 launches from 119 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, 89.5% wear one that more than one creator wallet has launched. See this ticker's page →

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

NameLFG Cooking
Metadata heldsha256 21b58769072a34b09ea36e5260ab52471b2569b782a606893d3e1b4684824219 · 21,895 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-10-23 18:44 UTC.
PictureNot captured, this launch declared none.

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