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

BROKE

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.

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

At launch

Created2026-10-02 10:25 UTC
CreatorAuffReBTkxCT3pJ4KHqkFrAsEWEqxTKBbb8v6jzC5ygZ
Creator took0.2% of supply in the first block
Outside buyers33 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 4.3 h ago and it was finished. Checked 2026-10-02 18:01 UTC.
Creator soldyes
Recorded from4YeoLZ1e6En3yG5Ei274FD… slot 452,582,599
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 10:25:53 UTC
Slot 452,582,599, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in5 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 10:26:54 UTC +1m 01s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 10:26:55 UTC +1m 02s
1.491e-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 4 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 254 launches from 201 creator wallets, including this one. See them →
This documentByte-identical to 2 other launches' metadata document. See them →
This creator5 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
NameBROKE FROG
Descriptiononly a broke frog bruh
Metadata heldsha256 9efc077a9b592de135b45f633e2cc9654b76923c3f5b911820a82c03fffea2b7 · 216 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 6feab1478fa079134cc8c524e75374a23e6c149d927f773e8644750e450305a5 · 52,462 bytes

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