POND
The curve completed 29s 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 29s after launch.
At launch
| Created | 2026-09-29 10:15 UTC |
| Creator | HdN3bsj4XHZ7zg9kFijfThQ4fgyLmRUMn5826PdYp8oB |
| Creator took | 5.0% of supply in the first block |
| Outside buyers | 214 distinct wallets, not counting the creator, bought on the bonding curve: 214 within the first 30s, 8 bundled into the creation block. |
| Graduated | 0 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 | 4zdzUEthwKdPtNZt1JBRD9… slot 451,612,093
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 10:15:49 UTC Slot 451,612,093, which is the chain's own clock for this moment. |
| Creation block | 8 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 10:16:18 UTC +29s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 214 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. |
| Highest price seen | 2026-09-29 12:57:28 UTC +2h 41m 40s
4.642e-6 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
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 | On 2 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 58 launches from 48 creator wallets, including this one. See them → |
| This creator | 1 earlier launch, 1 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 125.0 SOL |
| Read from chain | 2026-09-30 20:06 UTC, just now |
What this launch claimed to be
| Name | Pair Pond |
| Description | A multiplayer fishing game where every fish is a real coin. Hold $POND to get a boat and catch coins. Play in your browser. |
| Metadata held | sha256 339f568fed0f662ea4e9d0fcc02a3ed326335001f0c7501a35fcc1eefc3038c9 · 383 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 10:16 UTC. |
| Picture held | sha256 a6eba6572900e9776862ee812107a5a87ff7dcf8527c307e53bc03862cd7a276 · 23,602 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 10:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.