Chain of Title
1,052,402 launches on record
Coverage from 2 Sep 2026
Archive read 13:05 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

CUMROCKET

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.

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.

D6K7wNVGhA2g3hPJFimggivRGUVSPtv6CFrHVC1D3iV1 Solscan
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 23.0% of supply at launch.
findingIt left the curve 0s after launch.

At launch

Created2026-09-29 11:53 UTC
Creator96rQConaysBkXgRKmnX4eRiZmjh9Taf36iX1sbowvmNM
Creator took23.0% of supply in the first block
Outside buyersunknown distinct wallets, not counting the creator, bought on the bonding curve.
Graduatedin the same batch of events as the launch
Curve, read 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 fromRcZHoaYj17yWhvQfCkSzKv… slot 451,634,058
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-09-29 11:53:31 UTC
Slot 451,634,058, which is the chain's own clock for this moment.
Curve completed2026-09-29 11:53:31 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 tickerOn 33 launches from 24 creator wallets, including this one. See them →

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

NameCumrocket
DescriptionRaydium CPMM
Metadata heldsha256 e56445fb4d37fea3edae98947820680c7555fde9e9afde8f8df3db211c5322c6 · 229 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.
PictureNot captured, so we cannot show what it published. That is our storage budget, not a finding about the launch.

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