JUPCOIN
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 5 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 3.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-21 08:50 UTC |
| Creator | J65r843xC6fgJAm9HUGc1aprB1RhJ1rJA1QdXNoo1hRW |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 5 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 3KDTFsm4fDFiV7kLJgChzM… slot 449,006,298
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-21 08:50:33 UTC Slot 449,006,298, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-21 08:50:33 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-21 08:50:33 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 | 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. |
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 | 3.6 SOL |
| Read from chain | 2026-09-22 12:51 UTC, just now |
What this launch claimed to be
| Name | JUPITERCOIN |
| Description | Jupiter got tired of being watched. So he stole a frequency, put on a beanie, and started broadcasting after midnight. |
| Metadata held | sha256 154b7f045d9b4446ed2fb71e320f57585e2168be73ac43262b889c30229ea316 · 446 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 09eec9777d1a8ce5e173b221c1a7b220dd9092980687efcbb1b4e0c4380f1ef9 · 186,995 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-21 08:50 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.