$MFRG
The curve completed 57s after 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.
findingIt left the curve 57s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-20 03:08 UTC |
| Creator | 67L7WFd2Zy5tAycPFg4YSBERu9bn7fVeNERamM2LYNwE |
| Creator took | 0.3% of supply in the first block |
| Outside buyers | 19 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Incomplete. We read the bonding curve account 1.2 days ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-09-20 03:10 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3yRwSvoWYVWpJaNiEQy2WL… slot 448,605,416
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-20 03:08:34 UTC Slot 448,605,416, 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 | 5 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-09-20 03:09:31 UTC +57s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-20 03:10:01 UTC +1m 27s
1.479e-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 75 launches from 49 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 77 launches from 51 creator wallets, including this one. See them → |
| This document | Byte-identical to 74 other launches' metadata document. See them → |
| This creator | 45 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-21 08:43 UTC, just now |
What this launch claimed to be
| Name | 🐸 Moon Frog |
| Metadata held | sha256 d6f54429b9fc0ce03b012e8353be1c1562f7735e46757c40f87c60ecddc02a0f · 205 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 bf192ad18e8ac2d18d44d4f3d4f23fc5f505da653db8ee40e7e128feab37ddce · 155,048 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-20 03:08 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.