SJ
The curve completed 19s 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 19s after launch.
noteOnly 2.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 22:52 UTC |
| Creator | 4NT8M4FEnWFUyaW3aVjtKxgD68iPZqNnefRvYfYHnAXc |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 61 distinct wallets, not counting the creator, bought on the bonding curve: 61 within the first 30s, 11 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 | 3QfCVCCxQHh1Ez461feNUW… slot 452,104,478
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 22:52:58 UTC Slot 452,104,478, which is the chain's own clock for this moment. |
| Creation block | 11 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-30 22:53:16 UTC +19s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 22:53:16 UTC +19s
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 | 61 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. |
| This ticker | On 68 launches from 44 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.5 SOL |
| Read from chain | 2026-10-01 05:28 UTC, just now |
What this launch claimed to be
| Name | Super Jotchua |
| Description | Small paws. Big cape. The official home of Super Jotchua $SJ |
| Metadata held | sha256 ff2e2e16fbe9e18928f1ae7fd570c507a5786572286d59794635ec212e0b5af8 · 382 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 644dfcfa8acf24a5b4b46aea6c69f7996a3fc15983d6d94684f084f72797ac00 · 174,400 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 22:52 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.