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

DRAIN

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

Gp2NQ2bpbgU46CisaGob18Xqwpa7zWq9Tz2q1Jqgpump Solscan pump.fun
noteThe creator took 42.3% of supply at launch.

At launch

Created2026-10-02 03:47 UTC
CreatorA6LK3ko8Sg5WpPu1NxCZeKhqwnHFpJzBvgBvpfqdyHFs
Creator took42.3% of supply in the first block
Outside buyers81 distinct wallets, not counting the creator, bought on the bonding curve: 6 within the first 30s, 2 bundled into the creation block.
Graduated14 min after launch
Curve, read on chainComplete. We read the bonding curve account 10.3 h ago and it was finished. Checked 2026-10-02 04:31 UTC.
Creator soldnot while we watched
Recorded from2waxe2edcs9iUXkerpnfec… slot 452,493,283
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 03:47:33 UTC
Slot 452,493,283, which is the chain's own clock for this moment.
Creation block2 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
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-10-02 04:01:32 UTC +13m 58s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 04:01:32 UTC +13m 58s
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 14 launches from 12 creator wallets, including this one. See them →

Pool

Liquidity105.0 SOL
Read from chain2026-10-02 14:48 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameDRAINED
Metadata heldsha256 9a723f4ceffdf60befa736d4591018a63e3f2fd79c7fee586069368f4135473f · 294 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 d2e0cc7804495fdaefbe2920190ef23bd1757c89fcc1a866fe042b03b9b7e8b9 · 131,895 bytes

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