1,153,255 launches on record
Coverage from 2 Sep 2026
Archive read 06:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

XMRS

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.

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

At launch

Created2026-10-01 05:04 UTC
CreatorAzEgxknLj5W911Y6R3K3XeS3JZRg1w43otMyKGqgQPe
Creator took20.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 fromkVWqZGCebf3ZDxMRtm3JmP… slot 452,187,730
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 05:04:02 UTC
Slot 452,187,730, which is the chain's own clock for this moment.
Curve completed2026-10-01 05:04:02 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 pictureOn 9 launches from 9 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 37 launches from 37 creator wallets, including this one. See them →
This documentByte-identical to 28 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
NameMonero Strategy
DescriptionLaunched on discord.gg/uxento
Metadata heldsha256 aefa8a576746dc992b6a78a09ba1d31c998bcd7b25e3bec3e5375fab118d06e5 · 435 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 0057b3713653b2a616e00484beaa2e3752f74d5a9ac8cf95dea9837b801b02bb · 182,235 bytes

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