583,468 launches on record
Coverage from 2 Sep 2026
Archive read 17:17 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

BRAINROT

The curve completed 18s after 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.

BZMeeq5h5DerZLbQCw3huUR7qfv3TbEk3F4yFiHPpump Solscan pump.fun
findingIt left the curve 18s after launch.
noteOnly 0.8 SOL of liquidity was in the pool just now.

At launch

Created2026-09-20 12:01 UTC
Creator2Ejh1nPQuPiG1MyQaMMcLjhQrH6sHwv4kYphaT5DzuZY
Creator took0.3% of supply in the first block
Outside buyers18 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 0 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.2 days ago and it was finished. Checked 2026-09-20 12:10 UTC.
Creator soldnot while we watched
Recorded from4VG3Pebin3ysMyoqLwqSPN… slot 448,725,458
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-20 12:01:07 UTC
Slot 448,725,458, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-09-20 12:01:25 UTC +18s
Confirmed against the venue's own completion state.
Highest price seen2026-09-20 12:01:27 UTC +20s
1.394e-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.
Thirty seconds in3 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.

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 pictureUsed by 48 other launches. Identical bytes, matched by sha256. See them →
This creator55 earlier launches. See the creator's launches →

Pool

Liquidity0.8 SOL
Read from chain2026-09-21 17:20 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameBRAINROT COIN
Metadata heldsha256 528c9d727520e3da6b9285da9d23a9cbdaf0fd4f97be7229aeef3741bae7721b · 199 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 5817b0ef5dd2073dfa3973ee1fabbdb3631c287131ea358a5d74c878f3e7ed37 · 65,954 bytes

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