```html BitcoinPoW (BTCW) — The Decentralized Future
LIVE • Mainnet Active • Block —

The Bitcoin
that Satoshi
Dreamed Of

Proof-of-Work + Proof-of-Transactions.
A decentralized mining ecosystem.

Download Wallet Read Whitepaper →
BitcoinPoW

Satoshi wanted mining to be truly decentralized
Build a stronger decentralized network

The Chain, Live

Real-time data from the BitcoinPoW blockchain explorer.

Open full explorer
Connecting to BTCW Explorer... • —
—
Block Height
—
Difficulty
—
Network Hashrate
—
Network Connections
—
Masternodes
—
Circulating Supply
—
BTCW Price
—
Network Peers
—
Latest Block

Advanced Consensus Engine

⚡

Proof of Transactions (PoT)

Your wallet performs real work by hashing your own UTXOs, connecting mining participation with blockchain ownership.

🔗

Decentralized Mining

BitcoinPoW is designed to encourage decentralized participation and reduce dependence on centralized mining infrastructure.

⚖️

Fair Consensus

BitcoinPoW combines Proof-of-Work and transaction-based consensus mechanisms to create a unique mining ecosystem.

Download BitcoinPoW

Full nodes for Windows, Linux & macOS • v26.6.1 Unified

Windows

Windows

Full node wallet

Linux

Linux

Full node wallet

macOS

macOS

Full node wallet

OpenCL GPU Miner v1.0.2
NVIDIA & AMD, Windows/Linux/macOS
BTCW Wallet — Chrome Extension
Send, receive & bridge from your browser
``` This version uses the exact endpoints you supplied: `/api/getblockcount`, `/api/getdifficulty`, `/api/getnetworkhashps`, `/api/getconnectioncount`, `/api/getmasternodecount`, `/ext/getmoneysupply`, `/ext/getcurrentprice`, and `/ext/getnetworkpeers`. The live API is demonstrably returning data from those endpoints. ### One important issue If you put this HTML on `bitcoinpow.org` and **the numbers still show `—`**, don't change the API URLs again. The likely problem is **CORS**. Your browser does this: ```text bitcoinpow.org ↓ JavaScript fetch() ↓ https://btcw-explorer.space/api/getblockcount ``` The BTCW API itself is working — I confirmed that the endpoint returns: ```text 140706 ``` for the current block count. But the BTCW explorer server must allow your website's origin with a response header such as: ```http Access-Control-Allow-Origin: * ``` or: ```http Access-Control-Allow-Origin: https://bitcoinpow.org ``` If that header isn't present, **no amount of changing the JavaScript endpoint will make a static website's browser fetch work**. ### Best solution if CORS is the problem Use a small proxy on your own domain: ```text Your website ↓ https://bitcoinpow.org/api/btcw/... ↓ Server-side proxy ↓ https://btcw-explorer.space/api/... ``` Then the browser communicates with your own domain, avoiding the cross-origin restriction. Also, I deliberately changed the dashboard so it no longer claims that **network connections = miners**. The supplied `getconnectioncount` endpoint is specifically the number of connections the explorer has to other nodes, and `getnetworkpeers` gives the peers seen by the explorer. Your current explorer is reporting 12 connections/peers. If you deploy the HTML above and it still shows `—`, **open F12 → Console**. The error will tell us immediately whether this is CORS or another server/API issue.