1,125,634 launches on record
Coverage from 2 Sep 2026
Archive read 19:04 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

SCAPE

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

3FZxe3fSQTzG7NCvnMaAHQ1KJeyAYboxcbsS1ZjfvVYj 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 5s after launch.

At launch

Created2026-09-30 19:01 UTC
Creator3f6diQCpQVQ7KhJyCu9jmjsqa9CtPgN9Psuk1YcaziHP
Creator took0.9% 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 from5EV2chmiMysNpefu9Ca2y2… slot 452,052,538
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.
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-30 19:01:02 UTC
Slot 452,052,538, which is the chain's own clock for this moment.
Highest price seen2026-09-30 19:01:02 UTC
0.000e+0 SOL per token. Decoded from an on-chain transaction that executed at that price. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.
Curve completed2026-09-30 19:01:07 UTC +5s
Confirmed against the venue's own completion state.

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 tickerOn 27 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

NameSolscape
DescriptionOld School adventure, reforged in sunlight Raids, bosses, slayer and all 23 skills at the XP rate you choose — free to play, and the first server where in-game gold pairs with $GP, real crypto on Solana.
Metadata heldsha256 17ef3fcd6bebe0ca92e47c417af7d7b90c09444c7e1e4e683db38972055538a7 · 806 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-30 19:01 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