SP
The curve completed 45s 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 45s after launch.
noteOnly 2.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 20:49 UTC |
| Creator | J6WH8H4aXXq6ZVF65pWCPsZLabrPb5W3h4VoN7XLQgz8 |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 65 distinct wallets, not counting the creator, bought on the bonding curve: 60 within the first 30s, 7 bundled into the creation block. |
| Graduated | 1 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 | 2TBouWDkLAukygsc5nhBRS… slot 451,754,052
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 20:49:55 UTC Slot 451,754,052, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 60 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 20:50:39 UTC +45s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 20:50:39 UTC +45s
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. |
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 230 launches from 173 creator wallets, including this one. See them → |
| This creator | 1 earlier launch, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-10-01 07:57 UTC, just now |
What this launch claimed to be
| Name | SOL Parasite |
| Metadata held | sha256 793342aaa402f2ad3de3497810cc151334bd40219c898d6afdf7a3d4af24c77a · 317 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 20:50 UTC. |
| Picture held | sha256 a195ce3e4b8ec12b415834e84fbacc0b2978f58214ac5c9e7671a62f8f339f4b · 106,972 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:49 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.