Chain of Title
544,442 launches on record
Coverage from 2 Sep 2026
Archive read 01:10 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

CNRYSPY

The curve completed 26s after 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.

12QNWfqKDGZcEwkvgDiYvUPd6PDL3Xejkksvti5bFbWu 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.
findingIt left the curve 26s after launch.

At launch

Created2026-09-18 14:53 UTC
CreatorCKzBiQwZyLyeUk3EF5ZS8Gno4mShvbqmNTotL6TQ52zo
Creator took0.0% of supply in the first block
Outside buyersunknown distinct wallets, not counting the creator, bought on the bonding curve.
Graduated0 min after 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 fromZgCyMiGdEcfcPJtmWzk1xT… slot 448,116,190
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-18 14:53:35 UTC
Slot 448,116,190, which is the chain's own clock for this moment.
Curve completed2026-09-18 14:54:01 UTC +26s
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 creator2 earlier launches, 2 confirmed graduated on chain. 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

NameMMO Ignite Canary SPYx
DescriptionA one-off lifecycle canary of the MMO Ignite Custom Launch, quoted in the SPYx tokenised stock. Not an investment. Its curve is deliberately tiny and it exists to prove the launch, trade, migration and fee-claim path on mainnet once.
Metadata heldsha256 12e5a32bb564d382f08dc9f999ce0f78656dc44e97bea956e30f543ca6d0caaf · 316 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, this launch declared none.

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