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

Children

The creator took 35% of supply at 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 creator has 85 other launches on record. 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. 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.

HZYMR8aKtXgqp8Ck9UYWLfURs6Gf1ifSd1qPF5brpump Solscan pump.fun

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.

noteThe creator took 35.5% of supply at launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-11 13:04 UTC
Creator7ufmve7ZSFCzuNcKRunYrGtyb2Ka1MXzkWwf7jZhVsmL
Creator took35.5% of supply in the first block
Outside buyersunknown 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: 187 within the first 30s, 13 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldyes
Recorded from4bu3ijs97KVoZojQ1DFcir… slot 446,163,927
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-09-11 13:04:29 UTC
Slot 446,163,927, which is the chain's own clock for this moment.
Creation block13 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Highest price seen2026-09-11 13:04:31 UTC +2s
3.124e-7 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.
Thirty seconds in187 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 56 launches from 42 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. See this ticker's page →
This creator85 earlier launches, 19 confirmed complete on chain, 2 with findings on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 55 other creator wallets, across 73 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. 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
NameLegion of Children
DescriptionLaunched on discord.gg/uxento
Metadata heldsha256 c90488c492af25ea0f2e85529a4a40ce53e114390fec350750def137fe1132b2 · 405 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 7d7cb30105db34e5cd9217fe985758eb15eead6dba6e8d576e59d850e30bfe8b · 37,370 bytes

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