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

Cassie

The creator took 25% 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.

DpLrtcrzJBheLc4Wvt75XRfwQ125sLxuLZWQkozpump Solscan pump.fun
noteThe creator took 24.9% of supply at launch.
noteThe creator sold while we were watching.

At launch

Created2026-10-02 15:22 UTC
CreatorEiwpFhN3LmoSTEbygYnpweUJDaHNfXX3Uho2PGRVPmr3
Creator took24.9% of supply in the first block
Outside buyers218 distinct wallets, not counting the creator, bought on the bonding curve: 69 within the first 30s, 7 bundled into the creation block.
Graduated2 min after launch
Curve, read on chainComplete. We read the bonding curve account 5.8 h ago and it was finished. Checked 2026-10-02 15:31 UTC.
Creator soldyes
Recorded from3LJDzpFQ2qnjXYB9mYDeGa… slot 452,649,376
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 15:22:35 UTC
Slot 452,649,376, which is the chain's own clock for this moment.
Creation block7 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in69 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 15:24:57 UTC +2m 22s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 15:24:57 UTC +2m 22s
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 17 launches from 14 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 145 launches from 114 creator wallets, including this one. See them →
This documentByte-identical to 3 other launches' metadata document. See them →
This creator15 earlier launches, 4 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 27 other creator wallets, across 24 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. 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
NameCassie The Chimpanzee
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 d027959cea600a99ed81fb883be2b317186fad179ddd732a8ea09540c7d4713e · 401 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 b65c31d61d8b0f85e5265ec4a4113b02289af6d436a9636833cb1453bbcafea4 · 54,352 bytes

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