$mse
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.
noteOnly 0.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 13:37 UTC |
| Creator | FugLqcsgGtkaJUjU4n7NCbhsv9iW78QocniKi56idYPZ |
| Creator took | 0.3% of supply in the first block |
| Outside buyers | 12 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 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 | RffYUequk8nZ39VWFhJmgX… slot 452,625,820
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 13:37:50 UTC Slot 452,625,820, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 3 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 13:38:52 UTC +1m 01s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 13:41:10 UTC +3m 19s
5.491e-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 517 launches from 177 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This creator | 37 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.3 SOL |
| Read from chain | 2026-10-02 18:05 UTC, just now |
What this launch claimed to be
| Name | The Amazon Monkey |
| Metadata held | sha256 3c36dbb55b40b31385c16601bd39c695e5ae4912e74f10977a6eae70cbad88f8 · 199 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 dc688c557e0de42366cab5bede4f9ca9c5c76c0d03871091d6066778df5245b5 · 28,012 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 13:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.