4,014,723 launches on record
Coverage from 2 Sep 2026
Archive read 07:44 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-22 01:06 UTC

RIZZMAS3

A9DEEHsFtidkrjKbX3fVrEEkH5sVh87P1CEBnJh34A7h Solscan

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

19.9%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
The curve completed in the same batch of events as the 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 32 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.

33launches on record from this creator wallet, this one included, over 2 days
20on 21 Nov, its busiest day
19different tickers; the one it used most is COCOA, 4 times
21 Nov: 2022 Nov: 13
21 NovThis creator wallet's launches per day (UTC)22 Nov
Its most recent other launches (UTC)TickerNameMint
22 Nov, 08:07Early You are here██████████
22 Nov, 07:10MWG Meme Wars General██████████
22 Nov, 06:46SANTA Official Saint Nicholas██████████
22 Nov, 04:02snowball snowball██████████
22 Nov, 03:05Bullmas Bullmas██████████
22 Nov, 02:28CATEMAS Catemas██████████
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.

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 0s after launch.

At launch

Created2026-11-22 01:06 UTC
CreatorGeR4qgwS3GHLkVBUghdiiEunWEaBUYeTgXhhTuKo7aN7
Creator took19.9% 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.
Graduatedin the same batch of events as the 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 from2XNfrxswzWSHd264PX5Pf7… slot 472,350,599
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.

Order of events

Created2026-11-22 01:06:35 UTC
Slot 472,350,599, which is the chain's own clock for this moment.
Curve completed2026-11-22 01:06:35 UTC
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 67 launches from 55 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 creator31 earlier launches, 5 confirmed complete on chain, 27 with findings on record. 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
NameRIZZMAS3
Description2y ago rizzmas did 100+M ~ last year rizzmas2 did 20M ~ this year we need to send higher rizzmas3 ! I will make site where Tiktok clipers will be paid for posting rizzmas3 on tiktok per views!
Metadata heldsha256 b971c605f592cc93b55f19b701adcf559fd725fa006a80e430961b15ef38f0aa · 545 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 c0cc2fb25db1460175a63e2c50a9e0272ea2be7ec67236acd3b992eba30e0070 · 69,554 bytes

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