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

HIGH

Only 4 outside buyers bought its curveRead 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.

3FakoxCgLNtV17QkSxtXSnXaQDGSYYVvhTUSkC8Apump Solscan pump.fun
findingOnly 4 outside buyers bought on the bonding curve before it graduated.

At launch

Created2026-09-29 21:05 UTC
Creator6pXoxnRW6L7jASUUfSzfbLYSkiTJ6neiqZAyNzq2NLLG
Creator took0.2% of supply in the first block
Outside buyers4 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 1 bundled into the creation block.
Graduated52 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-30 03:32 UTC.
Creator soldnot while we watched
Recorded from5GZRWppTpKXS7ECLA6JCoV… slot 451,757,442
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-29 21:05:08 UTC
Slot 451,757,442, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in4 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-29 21:56:54 UTC +51m 46s
Confirmed against the venue's own completion state.
Highest price seen2026-09-29 21:56:54 UTC +51m 46s
1.154e-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 tickerOn 70 launches from 42 creator wallets, including this one. See them →
This creator654 earlier launches, 7 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 22 other creator wallets, across 58 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets →

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
NameHIGHEST EVER
Metadata heldsha256 808b86bb7935188e798b733c073eb45e02606b7fb7d5242e8d9bba68f9c395e5 · 194 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-30 21:06 UTC.
Picture heldsha256 51d12f471c90b02cacf9b2b876c85663b72f281fa3ca9674362f7ff74a50d009 · 365,864 bytes

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