3,913,233 launches on record
Coverage from 2 Sep 2026
Archive read 00:25 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-19 22:36 UTC

$COOKED

COOKED

6rZ9w9WY1Z1qp5jfdLkA7dJZ4Pd6WBRjQQMNGwoepump Solscan pump.fun

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

0.5%of supply taken by the creator in the first block
20outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 29s 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 19 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.

20launches on record from this creator wallet, this one included, over 4 days
9on 16 Nov, its busiest day
17different tickers; the one it used most is $REKT, 3 times
16 Nov: 917 Nov: 219 Nov: 420 Nov: 5
16 NovThis creator wallet's launches per day (UTC)20 Nov
Its most recent other launches (UTC)TickerNameMint
20 Nov, 05:55GIGACAT GIGACAT██████████
20 Nov, 05:50GIGACAT GIGACAT██████████
20 Nov, 03:40$REKT $REKT██████████
20 Nov, 03:20$REKT $REKT██████████
20 Nov, 03:04$REKT $REKT██████████
19 Nov, 23:30$LIQ $LIQ██████████
See all of this creator's launches →

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.

findingIt left the curve 29s after launch.

At launch

Created2026-11-19 22:36 UTC
Creator3tyLyij7ijTshnFYg4HbcgoYQfFMzh59CJSG511yexHj
Creator took0.5% of supply in the first block
Outside buyers20 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: 5 within the first 30s, 0 in the very same block the token was created in.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 7.0 h ago and it was finished. Checked 2026-11-19 23:06 UTC.
Creator soldnot while we watched
Recorded fromGj6VFvkqUs63GxRMAmDbMK… slot 471,505,269
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_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.

Order of events

Created2026-11-19 22:36:41 UTC
Slot 471,505,269, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-11-19 22:37:10 UTC +29s
Confirmed against the venue's own completion state.
Thirty seconds in5 distinct buyers, within the first thirty seconds.
A snapshot taken off a tick at the thirty-second mark, so it carries no moment of its own; it is placed here because that is where it happened.

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 60 launches from 50 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.9% wear one that more than one creator wallet has launched. See this ticker's page →
This creator14 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches →

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
NameCOOKED
DescriptionWe’re not early. We’re not late. We’re just cooked. $COOKED is the official coin for everyone who looked at the chart, felt the pain, and simply whispered: „yeah… we’re cooked.“ No false hope. No delusional hopium. Just pure acceptance and dark humor. This is for the ones who: • Bought the top with confidence • Averaged down like it was a strategy • Still refresh the chart every 11 seconds • And somehow find peace in being completely cooked $COOKED doesn’t promise the moon. It promises that when everything burns… at least we’ll burn together. Welcome to the cooked club. Membership is permanent.
Metadata heldsha256 512c8c6ccb0d2ceafc4ebc8ace444ecd0436cda3989ee9750d692d0ee4a7dab2 · 943 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 8bd3ee2f5d0a3991589b8f452bac0cd97dc67bacd995ca1fa0a8d054514e6528 · 206,726 bytes

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