730,406 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

MGOAT

Only 2 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.

GXnwGLoKyYnVBtNKuM5SU1kYmB4CjeLa653Xtmfjpump Solscan pump.fun
findingOnly 2 outside buyers bought on the bonding curve before it graduated.

At launch

Created2026-09-24 21:29 UTC
Creator7Pn9SEQfa9vmb3q3iYLDP4omUAFxfyfGxJXkZq4t5k9P
Creator took0.2% of supply in the first block
Outside buyers2 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 1 bundled into the creation block.
Graduated51 min after launch
Curve, read on chainComplete. We read the bonding curve account 2.6 h ago and it was finished. Checked 2026-09-25 01:23 UTC.
Creator soldnot while we watched
Recorded fromwkVYk6wkZUJgW64K3w8Lt6… slot 450,150,699
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-24 21:29:55 UTC
Slot 450,150,699, 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 in1 distinct buyer, 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:20:46 UTC +50m 52s
Confirmed against the venue's own completion state.
Highest price seen2026-09-24 22:22:18 UTC +52m 24s
1.190e-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 349 launches from 130 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 362 launches from 132 creator wallets, including this one. See them →
This documentByte-identical to 344 other launches' metadata document. See them →
This creator7 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
NameMoonGoat
Metadata heldsha256 a0e94860063ec8ded82e4ccfd0a0b9649be9106fa18bb811926e74db1ac98da9 · 191 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 33e3a5d3b399a49d05d2020c4d0af9cc0c945b537815513df1ee11071664d482 · 189,777 bytes

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