3Z6z1hPySNkFeB7HiKPCgqu4TZez.rig1

payout → 3Z6z1hPySNkFeB7HiKPCgqu4TZez

PPS balance

Payouts flow to your Thunder address on a cadence once the pool's Thunder reserve is funded. Ask the operator if you've been "Owed" a substantial balance for a long time and it isn't dropping.

Audit — why is this number what it is?

Every accepted share credits your worker FLOOR(share_difficulty × 1,000) sats. The rate is pps_sats_per_diff from the pool's config; the difficulty is what the pool held you at when the share landed (vardiff adjusts it based on how fast you're finding hashes). Everything below is derivable from the raw shares table — the stored balance is a running total the pool maintains, but you can always recompute it from scratch.

For an even deeper trail (per-share running total, daily breakdown), the operator has an admin-only page at /admin/worker/<id>. Same numbers — just without exposing other miners' data on this public page.

Payouts to your Thunder address

Each row is one Thunder transaction the pool sent to your address. Verify by looking the txid up in your own Thunder wallet — the same tx should show as an incoming credit.

Total paid to date: 111,426,303 sats (1.11426303 BTC) across 3 transactions.

Blocks you found

Blocks where your share crossed the network target. Even though PPS pays you the same per share regardless of whether a share becomes a block, blocks are what actually fund the pool BTC wallet that later gets deposited to Thunder to pay you. Look up the coinbase of each block with bitcoin-cli getblock <hash> 2.

25 blocks found · pool BTC earned: 125,000,000,000 sats (1250.00000000 BTC)

Hashrate · 10-min buckets · last 24h

Recent shares (last 200; worker target diff = 0.001)