Link Search Menu Expand Document

Block Explorer

Run your own block explorer without depending on external services.

Table of contents

  1. Run your own block explorer
  2. Preparations
    1. Transaction indexing
    2. Install NodeJS
    3. Firewall
  3. BTC RPC Explorer
    1. Installation
    2. Configuration
    3. First start
    4. Autostart on boot
    5. Remote access over Tor (optional)
  4. Upgrade

Run your own block explorer

After the RaspiBolt runs your own fully validated node, and maybe even acts as a backend for your hardware wallet with Electrs, the last important puzzle piece to improve privacy and financial sovereignty is your own Block Explorer. This lets you query transactions, addresses and blocks of your choice. You no longer need to leak information by querying a third-party block explorer that can be used to get your location and cluster addresses.

BTC RPC Explorer provides a lightweight and easy to use web interface to accomplish just that. It’s a database-free, self-hosted Bitcoin block explorer, querying Bitcoin Core and optionally Electrs via RPC. Built with Node.js, express, bootstrap-v4.


Transaction indexing

For the BTC RPC Explorer to work, you need your full node to index all transactions. Otherwise, the only transactions your full node will store are the ones pertaining to the node’s wallets (which you probably are not going to use). If not already enabled, you need to set the txindex parameter in your Bitcoin Core configuration file (bitcoin.conf): Bitcoin node configuration.

After adding the parameter, just restart Bitcoin Core with sudo systemctl restart bitcoind.

As reindexing can take more than a day, you can follow the progress using sudo tail -f /mnt/ext/bitcoin/debug.log.

Install NodeJS

  • Starting with user “admin”, we switch to user “root” and add the Node JS package repository. We’ll use version 12 which is the most recent stable one. Then, exit the “root” user session.

    $ sudo su
    $ curl -sL | bash -
    $ exit
  • Install NodeJS using the apt package manager.

    $ sudo apt-get install nodejs


  • Configure firewall to allow incoming HTTP requests from your local network to the web server.

    $ sudo ufw allow from to any port 3002 comment 'allow BTC RPC Explorer from local network'
    $ sudo ufw status

BTC RPC Explorer


We do not want to run the explorer code alongside bitcoind and lnd because of security reasons. For that we will create a separate user and we will be running the code as the new user. We are going to install the BTC RPC Explorer in the home directory since it doesn’t take much space and doesn’t use a database.

  • Create a new user with your password [ A ] and open a new session

    $ sudo adduser btcrpcexplorer
    $ sudo su - btcrpcexplorer
  • Download the source code directly from GitHub and install all dependencies using NPM. Since the program is written in JavaScript, there is no need to compile.

    $ git clone --branch v2.0.1
    $ cd btc-rpc-explorer
    $ npm install


  • Copy and edit the configuration template (skip this step when updating)

    $ cp .env-sample .env
    $ nano .env
  • By default, the BTC RPC Explorer listens for local requests (localhost / If you would like to access it from your local network or from somewhere else, make sure you configure the proper host and port by changing these parameters:

  • We instruct BTC RPC Explorer to connect to local Bitcoin Core by uncommenting and changing the following lines:

  • To compensate for the limited resources of the Raspberry Pi, let’s extend the timeout period.

  • To get address balances, either an Electrum server or an external service is necessary. It is important to use local RaspiBolt Electrs server, no real privacy is gained when we query external services anyway. The following configuration also works with Electrum Personal Server or ElectrumX.

  • You can go further improve your privacy by enabling privacy mode, but you won’t get certain feature like price exchange rates.

  • Make sure the RPC methods are not all allowed to avoid unnecessary security leaks. However, if you want to use the BTC RPC Explorer to send RPC commands to your node you might want to activate this with caution.

  • Additionally, if you want or need to see more logs related to the functioning of the explorer, you can enable them by changing this line with the proper parameter. Here we are adding logs from the ‘www’ (http server) module.

  • Save and exit

First start

Test starting the explorer manually first to make sure it works.

  • Let’s do a first start to make sure it’s running as expected. Make sure we are in the BTC RPC Explorer directory and start the web server.

    $ cd ~/btc-rpc-explorer
    $ npm run start
  • Now point your browser to http://raspibolt.local:3002 (or whatever you chose as hostname) or the ip address (e.g. You should see the home page of the BTC RPC Explorer.

    BTC RPC Explorer home screen with dark theme

  • If you see a lot of errors on the RaspiBolt command line, then Bitcoin Core might still be indexing the blockchain. You need to wait until reindexing is done before using the BTC RPC Explorer.

  • Stop the Explorer in the terminal with Ctrl-C and exit the “btcrpcexplorer” user session.

    $ exit

Autostart on boot

Now we’ll make sure our block explorer starts as a service on the Raspberry Pi so it’s always running. In order to do that we create a systemd unit that starts the service on boot directly after Bitcoin Core.

  • As user “admin”, create the service file.

    $ sudo nano /etc/systemd/system/btcrpcexplorer.service
  • Paste the following configuration. Save and exit.

    # RaspiBolt: systemd unit for BTC RPC Explorer
    # /etc/systemd/system/btcrpcexplorer.service
    Description=BTC RPC Explorer bitcoind.service
    # If you use an Electrum server, uncomment the following line and make sure to use the correct the service
    # After=electrs.service
    ExecStart=/usr/bin/npm start
    # Restart on failure but no more than 2 time every 10 minutes (600 seconds). Otherwise stop
  • Enable the service, start it and check log logging output.

    $ sudo systemctl enable btcrpcexplorer.service
    $ sudo systemctl start btcrpcexplorer.service
    $ sudo journalctl -f -u btcrpcexplorer
  • You can now access your own BTC RPC Explorer from within your local network by browsing to http://raspibolt.local:3002 (or your equivalent ip address).

Remote access over Tor (optional)

Do you want to access your personal block explorer remotely? You can easily do so by adding a Tor hidden service on the RaspiBolt and accessing the BTC RPC Explorer with the Tor browser from any device.

  • Add the following three lines in the section for “location-hidden services” in the torrc file. Save and exit.

    $ sudo nano /etc/tor/torrc
    ############### This section is just for location-hidden services ###
    HiddenServiceDir /var/lib/tor/hidden_service_btcrpcexplorer/
    HiddenServiceVersion 3
    HiddenServicePort 80
  • Restart Tor and get your connection address.

    $ sudo systemctl restart tor
    $ sudo cat /var/lib/tor/hidden_service_btcrpcexplorer/hostname
  • With the Tor browser, you can access this onion address from any device. Please be aware that this access is not password protected and should not be shared widely.

Congratulations! You now have the BTC RPC Explorer running to check the Bitcoin network information directly from your node.


Updating to a new release should be straight-forward, but make sure to check out the change log first.

  • From user “admin”, stop the service and open a “btcrpcexplorer” user session.

    $ sudo systemctl stop btcrpcexplorer
    $ sudo su - btcrpcexplorer
  • Fetch the latest GitHub repository information and check out the new release:

    $ cd ~/btc-rpc-explorer
    $ git fetch
    $ git checkout v2.0.1
    $ npm install
    $ exit
  • Start the service again.

    $ sudo systemctl start btcrpcexplorer

Next: Bonus guides »