btcmonitor

A terminal dashboard (TUI) that monitors a local Bitcoin Core node using its JSON-RPC interface.

• Cross-platform using Python3 and Rich: tested on macOS, Ubuntu, Windows
• Reads RPC credentials from the auth cookie or bitcoin.conf, with optional command-line overrides
• Visualizes the following data about your bitcoin node in a dashboard:
  • Node health, blockchain height, peer information
  • Network traffic, connection types, encrypted (v2) transport and peer client versions
  • Bitcoin price, block subsidy, # of blocks until next halving, time since last block
  • Mempool transaction count, memory size and fee histogram
  • Next block template as well as expected tx count, weight, and fee rate bands
  • Fee estimates from Bitcoin Core for confirmation within 2, 3 and 6 blocks and one day
  • The last five blocks with age, transactions, size, fees and mining pool
  • Scrollable list of the 100 largest transactions in the mempool sorted by BTC output
  • While the node is syncing: progress, blocks per second and estimated time to completion

Installation

btcmonitor needs Python 3.11 or later. Ubuntu 24.04 and later ship a recent enough Python; on older releases install a newer Python first.

With pipx (recommended)

pipx installs command-line tools into their own environment and puts them on your PATH:

pipx install btcmonitor

To upgrade later, run pipx upgrade btcmonitor. If you don't have pipx yet: sudo apt install pipx on Ubuntu/Debian, brew install pipx on macOS, or python -m pip install --user pipx on Windows, followed by pipx ensurepath.

From source

On macOS and Linux, pip needs a virtual environment:

git clone https://github.com/afalk42/btcmonitor
python3 -m venv ~/.venv/
source ~/.venv/bin/activate
cd btcmonitor
pip install -e .

On Windows 11 a virtual environment is not required:

git clone https://github.com/afalk42/btcmonitor
cd btcmonitor
pip install -e .

Usage

btcmonitor --help

By default it auto-discovers the datadir and cookie file for the default network (mainnet). You can override:

btcmonitor --network mainnet --rpc-host 127.0.0.1 --rpc-port 8332 --rpc-user user --rpc-password pass

Settings are resolved in this order: command-line options (or the BITCOIN_* environment variables), then bitcoin.conf, then defaults. From bitcoin.conf btcmonitor reads rpcuser, rpcpassword, rpcport, rpccookiefile and datadir, honoring network sections such as [signet]. It looks for bitcoin.conf in the data directory; use --conf to point elsewhere.

If no user and password are configured, cookie authentication will be attempted. If your node uses a non-default data directory, pass it with --datadir (or BITCOIN_DATADIR) so the cookie can be found.

--network accepts mainnet, testnet (alias testnet3), testnet4, signet and regtest. Unless --rpc-port is given, the network's standard RPC port is used (8332, 18332, 48332, 38332 and 18443 respectively).

Price and privacy

The BTC price comes from the public CoinGecko API, queried about once a minute. That request reveals this machine's IP address to CoinGecko. To avoid it, run with --no-price (or set BTCMONITOR_NO_PRICE=1): no price request is made and the fiat columns are hidden.

--currency (or BTCMONITOR_CURRENCY) selects the currency for the price and the transaction values, e.g. --currency eur. Any currency CoinGecko quotes works; an unsupported one is reported in the Bitcoin panel.

Requirements

• Python 3.11+
• A running bitcoind with JSON-RPC enabled (default on loopback)

Features

• Node summary: block height, headers, verification progress, peers, mempool bytes/txs, difficulty
• System stats: CPU, memory, swap, uptime, load average
• Network: download/upload rate (10-second average), traffic since node start, outbound connection types, peers using BIP324 encrypted v2 transport, and the most common peer client
• Mempool visualization: fee buckets with ASCII bars
• Next block projection: approximate composition derived from getblocktemplate or mempool fees
• Recent blocks: the last five blocks with height, age, transaction count, size, total fees and the mining pool read from the coinbase tag (best effort; unknown pools show their raw tag)
• Fee estimates: estimatesmartfee for 2, 3 and 6 blocks and one day (144 blocks), in sat/vB; Bitcoin Core's shortest target is 2 blocks
• Bitcoin price, block subsidy, # of blocks until next halving, time since last block
• Scrollable list of the 100 largest transactions in the mempool sorted by BTC output
• Initial block download view: replaces the mempool panels while the node syncs, with progress, blocks remaining, blocks per second, estimated time left (extrapolated from verification progress over the last two minutes), the date of the block being validated and size on disk

Keys

• ↑/↓, PgUp/PgDn, Home/End: select a transaction in the largest-transactions list
• Enter: show the selected transaction's details: size, fee, time in the mempool, RBF signalling, unconfirmed ancestors and descendants, and its inputs and outputs with addresses and amounts
• Esc, ← or Enter: back from the details
• q or Ctrl+C: quit

Refresh rate

--refresh sets how often the display redraws and the node is polled (default 2 Hz). The mempool histogram and the next-block projection, which require fetching the whole mempool and a block template, are refreshed every 5 seconds and whenever a new block arrives. The largest-transactions list looks up new mempool transactions in the background about once a minute.

Tests and linting

After installing the project with its development extras in your virtual environment, run:

pip install -e ".[dev]"
python -m unittest discover -v
ruff check .
ruff format --check .

The tests run offline and do not require a Bitcoin Core node. GitHub Actions runs the same checks on every push and pull request.

See CHANGELOG.md for what changed in each version and RELEASING.md for how releases are published to PyPI.

Project layout