Jumper
The curve completed 36s 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 36s after launch.
noteOnly 0.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 14:56 UTC |
| Creator | GbAieSbX2jXKi9KdEMAxXKeqcataXGRQJMv1BaQ1Ceia |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 29 distinct wallets, not counting the creator, bought on the bonding curve: 9 within the first 30s, 1 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Incomplete. We read the bonding curve account 1.3 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-29 15:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4MtJGGJba53xpNrvC1nGPC… slot 451,675,103
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 14:56:51 UTC Slot 451,675,103, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| 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. |
| Curve completed | 2026-09-29 14:57:26 UTC +36s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 14:57:26 UTC +36s
1.250e-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 | No other launch we hold a picture for used this one. |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
| This creator | 11 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.3 SOL |
| Read from chain | 2026-09-30 21:44 UTC, just now |
What this launch claimed to be
| Name | JUMP |
| Metadata held | sha256 6ffade80855072ef7eaadba977d02333a42e9b6e110a4d83627e82d0b0053701 · 224 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 14:58 UTC. |
| Picture held | sha256 e7f1a2c2fc6b6a2e05b10c1cb95cc64be538fc94d7ff15a05237c1937b116d06 · 12,224 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 14:56 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.