GOAT
The creator took 40% 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.
noteThe creator took 39.9% of supply at launch.
noteOnly 16.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 04:25 UTC |
| Creator | 2E98U45YoS4Eor8XVcPvhfojCWQ9c8QDKGTGtqWs5cQU |
| Creator took | 39.9% of supply in the first block |
| Outside buyers | 437 distinct wallets, not counting the creator, bought on the bonding curve: 149 within the first 30s, 1 bundled into the creation block. |
| Graduated | 3 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 2CVsQauRt1Qnt82jmwNyEf… slot 452,501,804
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 04:25:38 UTC Slot 452,501,804, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 149 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 completed | 2026-10-02 04:28:30 UTC +2m 53s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 04:28:30 UTC +2m 53s
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 picture | On 5 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 317 launches from 271 creator wallets, including this one. See them → |
Pool
| Liquidity | 16.1 SOL |
| Read from chain | 2026-10-02 13:28 UTC, just now |
What this launch claimed to be
| Name | Goatseus Maximus |
| Metadata held | sha256 f6e1bb8df85eeb696276511a4f7584bdb40148970d33f515315246e6689f95d7 · 498 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 held | sha256 4015c971963a7fab912269e3bac1710e0e805f847b0fc9d05937bc231f7d66fc · 5,659 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 04:25 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.