JEMUS
The curve completed in the same batch of events as the 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.
findingOnly 9 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 2.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 11:00 UTC |
| Creator | 4oUxGLVnyxUPiELyHB3RYMao4Ebh5pSPosbk28EjkPQR |
| Creator took | 0.1% of supply in the first block |
| Outside buyers | 9 distinct wallets, not counting the creator, bought on the bonding curve: 9 within the first 30s, 9 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-29 11:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4QQAcW5wqJNrCeeo6Ptb3k… slot 451,622,120
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 11:00:25 UTC Slot 451,622,120, which is the chain's own clock for this moment. |
| Creation block | 9 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 11:00:25 UTC +0s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 11:00:25 UTC +0s
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. |
| Thirty seconds in | 9 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. |
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 | No other launch we hold a picture for used this one. |
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-09-30 17:38 UTC, just now |
What this launch claimed to be
| Name | JEAN MUSCLE |
| Description | AFTER HOURS. ABOVE YOUR WEIGHT. |
| Metadata held | sha256 174aa7db57d4605aedb5992b1e8ecf156773b997b11aa5413396a5c93e927914 · 366 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 11:02 UTC. |
| Picture held | sha256 db006757cd089316b97d1f629b9394a69c08a7645db23996e7008b001d5c0a72 · 219,678 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 11:00 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.