605,073 launches on record
Coverage from 2 Sep 2026
Archive read 21 Sep 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

RICH

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.

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

At launch

Created2026-09-20 17:37 UTC
CreatorEm1RBcEsJickipHy1A1FSDifpUaWtTm7t3LRLrBSGkn5
Creator took0.3% of supply in the first block
Outside buyers20 distinct wallets, not counting the creator, bought on the bonding curve: 6 within the first 30s, 0 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-20 19:40 UTC.
Creator soldyes
Recorded from454ZBgeMZd6U4u1yZLiem1… slot 448,801,052
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-20 17:37:03 UTC
Slot 448,801,052, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
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-20 17:38:29 UTC +1m 26s
Confirmed against the venue's own completion state.
Highest price seen2026-09-20 17:39:56 UTC +2m 53s
2.681e-6 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 7 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 178 launches from 128 creator wallets, including this one. See them →
This documentByte-identical to 9 other launches' metadata document. See them →
This creator43 earlier launches, 0 confirmed graduated on chain. See the creator's launches →

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
NameRICHCOIN
DescriptionEVILcoin helps fund Reteps evil plans for conquest, also his BMW
Metadata heldsha256 a46c3b6c3521879ab781971d4d37c965064c52642e76eb43bf3d86d10ea57ca8 · 254 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-21 17:37 UTC.
Picture heldsha256 888db7be359405457c5c0b8ae1f528539a103f25ddac76e7d2e69f29c7b52fa4 · 535,329 bytes

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