3,234,599 launches on record
Coverage from 2 Sep 2026
Archive read 14:19 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

ROCCO

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 picture is on 3 other launches from 3 creator wallets in all. 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. Across the archive, 55.4% of the launches whose picture we hold carry one a different creator also used. 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.

mV9kZc5WEcsupy9KYZo1c7x52Ys1A5CDK73Ysg6pump Solscan pump.fun

Cite this record as: Chain of Title, ROCCO, mint mV9kZc5WEcsupy9KYZo1c7x52Ys1A5CDK73Ysg6pump, observed at creation 2026-11-06 13:38 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/mV9kZc5WEcsupy9KYZo1c7x52Ys1A5CDK73Ysg6pump

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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

At launch

Created2026-11-06 13:38 UTC
CreatorC93dL5X5gSioSZWU72X6BSC12vRF87DoTNXtsumwt2tE
Creator took0.2% of supply in the first block
Outside buyers16 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 soldno
Recorded fromUGpZxkaMN7Kr1MaiBA3cRQ… slot 466,129,106
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-06 13:38:19 UTC
Slot 466,129,106, which is the chain's own clock for this moment.
Creation block16 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-06 13:38:19 UTC +0s
Confirmed against the venue's own completion state.
Thirty seconds in16 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 pictureOn 4 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55.4% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 144 launches from 124 creator wallets. 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.3% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 3 other launches, across 3 creator wallets in all. Across the archive, 32.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 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. Across the archive, 63.8% of launches come from a creator linked to at least one other wallet this way. 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
NameROCCO
DescriptionDog eats rocks
Metadata heldsha256 207529d9832dfa0e8be926f32a6a8bc763deecc44bc3e3df5cf76966bdedd1d5 · 249 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 b1d70d349e4e91d8b342d60c06e6316ad7817937e42ee41793f150174b3ebe7c · 3,239,263 bytes

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