1,190,800 launches on record
Coverage from 2 Sep 2026
Archive read 1 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

baton

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

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

At launch

Created2026-10-01 19:41 UTC
Creator4KWxZgfPgSTNCT1N7E7obxfHdywB2vNNrbUgGXKyN9yp
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 from4oK7DinrpiBvdaputgRtvT… slot 452,384,399
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-10-01 19:41:16 UTC
Slot 452,384,399, which is the chain's own clock for this moment.
Curve completed2026-10-01 19:41:18 UTC +2s
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 pictureOn 64 launches from 39 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 417 launches from 277 creator wallets, including this one. See them →
This documentByte-identical to 15 other launches' metadata document. 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

The picture this launch published at birth
Namebaton
DescriptionCreated on https://rapidlaunch.io
Metadata heldsha256 b0cc19c66ab0e98ada7202e6fc17db593ec093054c552c0348f2b46ce9b1b923 · 385 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 45d46d18d4a65c0765cde6732043d7a9457c8550fc347de90a07088c2ace674d · 3,796 bytes

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