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

www

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.

91gwzoFp3nxwsPw5KJfvAxnYtzJZvEzxNLVnJcxNpump Solscan pump.fun
noteThe creator sold while we were watching.

At launch

Created2026-10-02 02:06 UTC
Creator6QTqkBSt4pgpcfzTHQPAoVCHPP9WsKc1mg1EdgFhvLVr
Creator took3.4% of supply in the first block
Outside buyers671 distinct wallets, not counting the creator, bought on the bonding curve: 58 within the first 30s, 5 bundled into the creation block.
Graduated15 min after launch
Curve, read on chainComplete. We read the bonding curve account 5.2 h ago and it was finished. Checked 2026-10-02 02:31 UTC.
Creator soldyes
Recorded from4FGRk4UJJ7UpVgTHyUUABC… slot 452,470,708
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 02:06:49 UTC
Slot 452,470,708, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in58 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-10-02 02:21:49 UTC +14m 59s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 02:21:49 UTC +14m 59s
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 12 launches from 11 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 52 launches from 35 creator wallets, including this one. 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
Nameworldwideweb
Metadata heldsha256 8c50693920221703086e7fc0743c9b44abee95815ed2f4a7446342e13e292f3f · 297 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 3963b8fbbbe33526ce8f7c2ee438428d8f9bda7adfa56adbca310539b2414a06 · 18,425 bytes

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