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

ROUTE

The creator took 50% of supply at 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.

J7cHQhHHMA7dZohpEE9aGSXgk9d9md7LQCctDRxypump 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.

findingThe creator took 50.0% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.

At launch

Created2026-09-02 20:42 UTC
CreatorB72NbEXhShcimXLk2He14ZWdQB592bjFexcNBPhzSxNS
Creator took50.0% 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: 76 within the first 30s, 4 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.
Graduated1 min after launch
Curve on chainComplete. We read the bonding curve account 25.1 days ago and it was finished. Checked 2026-09-09 23:50 UTC.
Creator soldnot while we watched
Recorded from5An5feXr6KyEB4NHN9h5ES… slot 443,790,902
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-02 20:42:39 UTC
Slot 443,790,902, which is the chain's own clock for this moment.
Creation block4 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in76 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.
Curve completed2026-09-02 20:43:45 UTC +1m 05s
Confirmed against the venue's own completion state.
Highest price seen2026-09-02 20:43:45 UTC +1m 05s
4.109e-7 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.

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 62 launches from 60 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 →

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
NameRemit Routes
DescriptionThe token powering RemitRoutes, the intelligence layer for global money movement, comparing banks, fintechs and crypto rails across hundreds of international transfer corridors.
Metadata heldsha256 b6e9d2cbc5a36e74475e2d049da40fe3aa7bfef65ed4dfea85274a20b2dadd91
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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-23 00:42 UTC.
Picture heldsha256 39b7d35585abed25ecb24d3a5492e0b7b507f6da5ecae95456576a5109029160 · 614,986 bytes

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