- Network Summary dashboard
- View details of blocks, transactions, and addresses
- Analysis tools for viewing stats on blocks, transactions, and miner activity
- See raw JSON content from bitcoind used to generate most pages
- Search by transaction ID, block hash/height, and address
- Optional transaction history for addresses by querying from ElectrumX, blockchain.com, blockchair.com, or blockcypher.com
- Mempool summary, with fee, size, and age breakdowns
- RPC command browser and terminal
See CHANGELOG.md.
- Install and run a full, archiving node - instructions. Ensure that your bitcoin node has full transaction indexing enabled (
txindex=1
) and the RPC server enabled (server=1
). - Synchronize your node with the Bitcoin network (you can use this tool while your node is still sychronizing, but some pages may fail).
- Install a "recent" version of Node.js (8+ recommended).
If you're running on mainnet with the default datadir and port, the default configuration should Just Work. Otherwise, see the Configuration section below.
npm install -g btc-rpc-explorer
btc-rpc-explorer
git clone git@github.com:janoside/btc-rpc-explorer.git
npm install
npm start
Using either method (npm install
or run from source), after startup open http://127.0.0.1:3002/
Configuration options may be set via environment variables or CLI arguments.
To configure with environment variables, you need to create one of the 2 following files and enter values in it:
~/.config/btc-rpc-explorer.env
.env
in the working directory for btc-rpc-explorer
In either case, refer to .env-sample for a list of the options and formatting details.
For configuring with CLI arguments, run btc-rpc-explorer --help
for the full list of options. An example execution is:
btc-rpc-explorer --port 8080 --bitcoind-port 18443 --bitcoind-cookie ~/.bitcoin/regtest/.cookie
docker build -t btc-rpc-explorer .
docker run -p 3002:3002 -it btc-rpc-explorer
See instructions here for using nginx+certbot (letsencrypt) for an HTTPS-accessible, reverse-proxied site.