732,337 launches on record
Coverage from 2 Sep 2026
Archive read 01:24 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

REFRO

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.

3ks4Kq7cThrcayAvLiqTfQpqLCtC97dPmJkdK24ppump Solscan pump.fun

At launch

Created2026-09-24 22:11 UTC
Creator2fcrdaQaED5bUru4mmk6R39JoKFaLBaVmnKk4RX7J11U
Creator took0.2% of supply in the first block
Outside buyers14 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 5.4 h ago and it was finished. Checked 2026-09-24 23:53 UTC.
Creator soldnot while we watched
Recorded from5cJuoBWbSsYcnoqaN2W5jD… slot 450,160,129
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-24 22:11:56 UTC
Slot 450,160,129, 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-09-24 22:12:59 UTC +1m 03s
Confirmed against the venue's own completion state.
Highest price seen2026-09-24 22:21:29 UTC +9m 33s
2.789e-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.

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
NameRelaxing frog
Metadata heldsha256 708025a817ec21f21256a9e45f498d65d030ca87499d279a7459ba51ac063d97 · 300 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 d6c3c16e069ed083e787de421652276f8d026db06dd52f3e1111e886e73d9e23 · 27,105 bytes

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