715,397 launches on record
Coverage from 2 Sep 2026
Archive read 16:24 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

0xPay

No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.

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.

Cmdj2aC7LKGCrXNoT85DDDekxtNQ7er3fTdNJwLZTSoL Solscan pump.fun
noteThe creator sold while we were watching.

At launch

Created2026-09-24 15:45 UTC
Creator4JZhWZP673xQj8qmHPsqmuDoS2UVUeT2WcnWqqXqns8t
Creator took3.4% of supply in the first block
Outside buyers955 distinct wallets, not counting the creator, bought on the bonding curve: 6 within the first 30s, 3 bundled into the creation block.
Graduated15 min after launch
Curve, read on chainComplete. We read the bonding curve account 3.9 h ago and it was finished. Checked 2026-09-24 16:23 UTC.
Creator soldyes
Recorded fromtLBaqQUBt45iKeyhBwCzyA… slot 450,073,349
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-24 15:45:45 UTC
Slot 450,073,349, which is the chain's own clock for this moment.
Creation block3 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in6 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-24 16:00:39 UTC +14m 54s
Confirmed against the venue's own completion state.
Highest price seen2026-09-24 16:00:39 UTC +14m 54s
4.109e-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.

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 pictureOn 5 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 5 launches from 4 creator wallets, including this one. See them →
This documentByte-identical to 1 other launch's metadata document. See them →
This creator1 earlier launch, 0 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. 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
Name0xPay
Description0xPay
Metadata heldsha256 8473e61291a32a5f5b8fce9889ddac9def5317d906f60a80e79add322176b482 · 269 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 1544412e2327d0c6201ccab731d5742603528de974035040758fc0d00375884b · 11,086 bytes

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