What the pool dashboard shows
MySoloPool publishes transparent Bitcoin solo mining pool statistics so miners and observers can verify activity on our stratum pool in near real time. Figures such as aggregate pool hashrate, active miner count, accumulated blocks credited to participants, and short-term performance trends are surfaced directly from pool operations—not estimates from third-party aggregators.
Historical charts on this page summarise how contribution has behaved over selectable windows (for example last day, seven days, or thirty days). They are intended for situational awareness: capacity changes, onboarding events, or maintenance windows often show clearly in smoothed series.
Bitcoin blockchain node data on this page
Alongside pool-side telemetry, MySoloPool exposes selected metrics from our Bitcoin Core (full node) deployment—including current chain tip height, headline network difficulty where applicable, peer connection counts aligned with RPC reporting, sync or verification posture, and protocol metadata consistent with Bitcoin's consensus layer. These readings help explain environmental context miners see when building on recent work: mempool pressure, propagation, and node health indirectly affect how candidates are assembled and propagated.
Node figures are labelled and grouped separately from purely pool-internal counters so visitors can distinguish what originates from miners connected to MySoloPool versus what reflects global peer-to-peer blockchain network conditions reported by our node at query time.
Solo mining luck and time-to-block planning
The solo mining luck calculator above uses live network hashrate from our Bitcoin node to estimate mean, median, and 90th-percentile time-to-block intervals. Solo mining on MySoloPool remains a lottery—transparent odds help you set realistic expectations before pointing hashrate at stratum.
Why transparency matters for solo pool participants
Solo mining shifts reward variance to independent operators; credible, inspectable dashboards reduce guesswork when evaluating uptime, competitiveness, or fee structures. Keeping pool statistics adjacent to reproducible blockchain node datapoints reinforces that payouts and chain state references align with the same Bitcoin ruleset your hashrate is helping extend.