AHOY
The curve completed 41s 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.
noteThe creator took 36.4% of supply at launch.
findingIt left the curve 41s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 20:20 UTC |
| Creator | 78Wto8uB28fzqQyKwwJf3Yn3KzBbCuMPG8c8Xu4oX3Rw |
| Creator took | 36.4% of supply in the first block |
| Outside buyers | 72 distinct wallets, not counting the creator, bought on the bonding curve: 72 within the first 30s, 0 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 | QcjPZfRuZMet9A21eomR1Z… slot 452,070,379
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 20:20:49 UTC Slot 452,070,379, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-09-30 20:20:49 UTC
0.000e+0 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 | 72 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-30 20:21:31 UTC +41s Confirmed: a PumpSwap pool was found for it. |
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 | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 00:03 UTC, just now |
What this launch claimed to be
| Name | PUMPFUN PIRATES |
| Description | Searching for booty |
| Metadata held | sha256 e8f6ac71c862495653c893b296d4efde60a79dcafa1c7730c175403300ca4142 · 298 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 e692034350f56f5ded0a80db5c9e41801cde6dff61efddee018554417a3cbfd3 · 175,736 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 20:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.