GOONAPE
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.
noteThe creator sold while we were watching.
noteOnly 3.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 00:35 UTC |
| Creator | Axszc4QgtgYZGMGZ1gKAfpk899Bky2AJM6qP6FU8xe3W |
| Creator took | 4.0% of supply in the first block |
| Outside buyers | 338 distinct wallets, not counting the creator, bought on the bonding curve: 37 within the first 30s, 16 bundled into the creation block. |
| Graduated | 11 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 | yes |
| Recorded from | 5pUcqmC288xDTyi7gkmn9H… slot 452,450,245
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 00:35:41 UTC Slot 452,450,245, which is the chain's own clock for this moment. |
| Creation block | 16 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 37 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 00:46:15 UTC +10m 34s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 00:46:15 UTC +10m 34s
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 421 launches from 31 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 421 launches from 31 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.1 SOL |
| Read from chain | 2026-10-02 06:59 UTC, just now |
What this launch claimed to be
| Name | GOONAPE |
| Description | $GOONAPE turns mouse strokes into points, combos, and a live leaderboard at a sunset villa 🍌 Every 10 minutes, top five players split ZEC rewards, while holders get remembered on the board 🌅🏆 |
| Metadata held | sha256 d60d88dba735aa2455780a61354b2277de41322fd16d8165565fc463a8a5381b · 581 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 3199ae9e8296041b0d3e20eb6a0459dda528856490cc4da3ba2321c65aa800f3 · 41,021 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 00:35 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.