SHARK
The curve completed 12s 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 12s after launch.
noteOnly 0.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 10:01 UTC |
| Creator | 66zstBUnfNRaa9ESx7Pe5zTYJgc9NPy9e5qKaHPmZWN1 |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 20 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Incomplete. We read the bonding curve account 1.5 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-30 10:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 2uXdAVWHxk2boCobDZvJdf… slot 451,931,707
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 10:01:46 UTC Slot 451,931,707, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-30 10:01:58 UTC +12s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 10:01:59 UTC +13s
1.582e-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 | 3 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 | On 3 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 98 launches from 79 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.2 SOL |
| Read from chain | 2026-10-01 21:28 UTC, just now |
What this launch claimed to be
| Name | Shark |
| Description | it's a shark. what else do you need? |
| Metadata held | sha256 beb95d2ba7d45da757042221fbed08734e4f69f1c2a369457687976ecbb2b66d · 328 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-10-01 10:03 UTC. |
| Picture held | sha256 4a5af48caac27177bf75e0d07eb622cf5946a00afdf33431f8654ae84806fe83 · 353,830 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 10:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.