PARAPAID
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 2.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 18:59 UTC |
| Creator | CqhGFkJJWYMcWCP7FA1W1W84VrNmAGhmFYQ7ZkycfU6k |
| Creator took | 0.4% 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 | Complete. We read the bonding curve account 1.2 days ago and it was finished. Checked 2026-09-29 19:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 2yJjiqqrVaPrcHz24SKh2q… slot 451,729,315
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 18:59:22 UTC Slot 451,729,315, 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-29 18:59:22 UTC +0s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 18:59:22 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. |
| This ticker | On 9 launches from 9 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.2 SOL |
| Read from chain | 2026-10-01 00:48 UTC, just now |
What this launch claimed to be
| Name | PARASITE PAID |
| Description | We checked the vents, changed the locks, and blamed Kevin. It was already in the group chat. |
| Metadata held | sha256 36396bf6a0b8efff1e1142a628f32cebb740ab953b43fcfe823cf47586e29d2f · 415 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 19:00 UTC. |
| Picture held | sha256 35093473b31ad9fb0b5bea94c0c50cf7514ea0e0b39cee7812d98b4e08420e32 · 135,148 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 18:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.