$PARWifHat
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 1.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 19:31 UTC |
| Creator | 4PunXj5Njonf2poVkHAjBQb5HVuMpdNiEnX6wHEjFhyS |
| 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.4 days ago and it was finished. Checked 2026-09-29 19:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4yMzvurHSDZvCs8jputmk7… slot 451,736,436
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 19:31:07 UTC Slot 451,736,436, 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 19:31:07 UTC +0s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 19:31:07 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 | 1.5 SOL |
| Read from chain | 2026-10-01 06:07 UTC, just now |
What this launch claimed to be
| Name | PARASITE WifHat |
| Description | Tiny tenant. Permanent hat. Currently borrowing your Wi-Fi. |
| Metadata held | sha256 f20449fec25988eb7f666eadb48cad6d5f3fe93fa58a212fcde1adfad9061990 · 385 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:32 UTC. |
| Picture held | sha256 fed8d595046f3297671adb158998a37b9c2de473bf9b6d9f5541b09cde4f4ac6 · 124,557 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 19:31 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.