DHIVA LABS · LEARN

Appearance

poolwatch ​

poolwatch shows the mempools of your own blockchain nodes side by side in a terminal. It talks directly to each node's RPC interface, so it needs no outside service, no database and no web browser.

A mempool (memory pool) is the set of transactions a node has received but that are not yet in a block. Watching it tells you how many transactions are waiting, how large the backlog is, what fee rates they pay and how fast new ones arrive. A node's RPC interface is the local HTTP API that the node software offers for tools like this one.

What it does ​

  • Watches several nodes at once. One dashboard row per node, each polled on its own, for monerod, oxend, beldexd, bitcoind and compatible forks.
  • Shows pool size and fee rates: transaction count, pool size in bytes, the median fee rate, and fee rate bands from the 10th to the 90th percentile.
  • Tracks arrivals and departures. poolwatch notes when it first sees each transaction, and from that works out the inflow rate (transactions per minute over 1, 5 and 15 minutes), how long transactions have been waiting, and how many have left the pool.
  • Flags instant transactions. Oxen Blink and Beldex Flash transactions are marked with ⚡.
  • Lists transactions in a table you can sort by fee rate, size or age, and filter by transaction ID.
  • Prints a one-off report with --once, for scripts and health checks.

Who it is for ​

  • People who run their own nodes and want to see what their mempool is doing from a terminal, including on a server without a desktop.
  • Developers and testers of wallets and node software who need to watch transactions enter and leave a pool.

What it does not do ​

poolwatch only reads from nodes. It has no wallet, cannot send or broadcast transactions, keeps no history between runs, and shows no market or price data. It sends nothing anywhere except requests to the RPC addresses in your configuration file.

Platforms ​

The released binary, version 0.1.0, is for Linux on x86-64. It is a static binary: it needs no libraries and runs on any recent distribution. You can build poolwatch from source for other targets, including Linux on ARM64 and Windows; see Install.

You need at least one supported node that you can reach over RPC, usually on the same machine.

Next steps ​