Use the Explorer over Tor

1Why bother

Every Divi transaction is public, so an explorer holds no secrets about the chain. What it can learn is about you. When you paste your address into any explorer, the site sees that address arrive from your internet connection. Do that every morning to check your stakes and the pairing is obvious: this connection owns that wallet.

Tor sends your request through three volunteer relays. The explorer sees the last relay's address instead of yours, and none of the relays sees both who you are and what you asked for.

Who needs this

Anyone who would rather not tie a wallet to a home or office connection: large holders, people in places where holding crypto draws attention, or anyone who simply prefers it. It costs a few seconds per page.

2Get Tor Browser

Go to torproject.org/download. Download only from there; copies elsewhere can be tampered with.
Install it like any other app. It is free and runs on Windows, macOS, Linux and Android.
Open it and choose Connect. The first connection takes a little while; after that it is quicker.

Tor Browser is a modified Firefox. Use it only for the things you want private, and keep your everyday browser for the rest.

3Open Explorer 2.0 through Tor

Type the normal address into Tor Browser:

https://services.divi.domains/explorer2/

That is all. The explorer works the same through Tor as without it. We loaded a block page, an address page and the CSV export through Tor and each came back normally, as did the testnet explorer at /testnet/explorer2/. Search, the Staking Intelligence tab and the export buttons need nothing extra.

What each party sees

Divi Services sees a request from a Tor exit relay, not from you. The exit relay sees that someone visited services.divi.domains, but the page, the address you typed and the answer travel inside HTTPS, so it cannot read them. Your internet provider sees only that you use Tor.

To read an address, paste it into the search box as usual. The look up an address tutorial explains what you will see.

4About the .onion address

The Divi Services home page lists a "Tor Access (Web)" onion address:

http://2b3tlgw57sro5arai43uxjav2ke4laqvsgesdpmti2zxazg6waz3gpqd.onion/

An onion address keeps the whole trip inside Tor, so no exit relay is involved. We opened it through Tor on 2026-10-22. It is the whole Divi Services site: the same home page, these tutorials and every tool, at the same paths as on services.divi.domains. Links on the onion keep you on the onion. For example:

/explorer2/: Explorer 2.0, and /testnet/explorer2/ for testnet
/explorer/: the classic explorer
/api/: the explorer API, for example /api/getblockcount
/api/rpc/: the public RPC service
/wallet/, /rpc/, /testnet/faucet/ and /chatbot/: the web wallet, the RPC playground, the testnet faucet and the assistant

For the most private lookups

Open the onion address above with /explorer2/ added, in Tor Browser. Explorer 2.0 then reads the chain through the onion as well, so no exit relay sees even the hostname. The normal address from step 3 also works.

The other onion on the home page, ending …uyd.onion:52472, is not a website. It is a Divi node for wallets and nodes to connect to over Tor. That is covered in run your node over Tor.

5Scripts and curl through Tor

If you check balances from a script, send that through Tor too. Tor offers a SOCKS proxy on your own computer. The tor service listens on port 9050. Tor Browser runs its own proxy while it is open, usually on port 9150.

# Confirm your requests leave through Tor
curl --socks5-hostname 127.0.0.1:9050 https://check.torproject.org/api/ip
# {"IsTor":true,"IP":"185.220.…"}

# Ask the public Divi RPC service for the block height, through Tor
curl --socks5-hostname 127.0.0.1:9050 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"1.0","id":1,"method":"getblockcount","params":[]}' \
  https://services.divi.domains/api/rpc/
# {"error":null,"id":1,"result":4269315}

Use --socks5-hostname, not --socks5. The longer form lets Tor look up the site's name, so your own internet provider never sees which site you asked for. The query the chain tutorial lists what else the RPC service answers.

6The other explorers

The classic explorer at /explorer/ and chainz at chainz.cryptoid.info both loaded through Tor in our test. The classic explorer is also on the Divi onion at /explorer/; chainz has no onion address. chainz sits behind a web protection service, so it may sometimes ask a Tor visitor to prove they are human; if it does, wait and reload. Explorer 2.0 and chainz side by side explains when to use which.

7What Tor does not hide

The chain itself. Your address, its balance and its history are public whether you use Tor or not. Tor hides who is looking, not what is there.
That the address was looked up. The explorer still sees a request for your address; it just cannot tell it came from you.
Anything you give away. Logging into an account, or opening the same address in your normal browser too, links you again.
Your wallet's own traffic. Tor Browser protects pages you open in it. A wallet app or a staking node makes its own connections; to route those through Tor, see run your node over Tor.

If something goes wrong

You see	What it means
Pages load slowly	Normal for Tor. Give each page a few extra seconds. If it stays slow, ask Tor Browser for a new circuit for this site from its menu.
The .onion opens the Divi Services home page, not the explorer	The onion is the whole site. Add `/explorer2/` to the address, or pick Explorer 2.0 on the home page.
curl says "Failed to connect to 127.0.0.1 port 9050"	The tor service is not running, or you are using Tor Browser's proxy. Start tor, or try port 9150 with Tor Browser open.
chainz shows a check page	Its protection service is unsure about the Tor relay. Wait a moment and reload, or use Explorer 2.0.
Explorer says "Block not found" or a blank page	Same causes as without Tor: a typo, or a hash from testnet pasted into mainnet. See read a block.

Still stuck? Ask the Divi chatbot, or see all tutorials.