1,247,602 launches on record
Coverage from 2 Sep 2026
Archive read 2 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

COOLBOT

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.

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

At launch

Created2026-10-02 07:53 UTC
CreatorDw7E8iMc8tdK88Qw7ezxiXxDfrHizFcHccx4L6ycKzmL
Creator took0.2% of supply in the first block
Outside buyers30 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 0 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 10.6 h ago and it was finished. Checked 2026-10-02 15:31 UTC.
Creator soldyes
Recorded from27gCRdT8ksEC1XZrDbqbaZ… slot 452,548,389
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 07:53:29 UTC
Slot 452,548,389, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in7 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 07:54:55 UTC +1m 26s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 07:54:56 UTC +1m 28s
2.341e-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 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This creator10 earlier launches, 1 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
NameCOOLBOT
DescriptionHOTBOTS COOL BROTHER
Metadata heldsha256 284dd8945977976dceea1c2945792476649fd2eec297fa3690455326d7fb1c6e · 213 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 3f2c0d51cffeec3aff48eff953120564e8f490ad33c872d33d2e84f623e9b500 · 441,448 bytes

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