Query the Chain Yourself

1Why ask the chain directly

An explorer page is a view of answers that came from a Divi node. Asking for those answers yourself is useful when you want to check one site against another, watch a number from a script, or keep a record without copying it off a screen.

Three public services answer questions about Divi mainnet, and none of them needs an account:

All the examples use curl and are written for a macOS or Linux terminal. On Windows, run them in WSL or Git Bash, because the Command Prompt and PowerShell treat the quote marks differently.

2Your first question: how tall is the chain?

The Divi RPC service takes a small piece of JSON that names a method and its parameters. Ask for the current block height:

curl -s https://services.divi.domains/api/rpc/ \
     -H 'Content-Type: application/json' \
     -d '{"jsonrpc":"1.0","id":"me","method":"getblockcount","params":[]}'

# reply
{"error":null,"id":"me","result":4269891}

The answer is in result. Your number will be higher: mainnet adds a block about every minute. The id is anything you like and comes back unchanged.

You can ask several questions in one request by sending a list. The service takes up to 20 at a time:

curl -s https://services.divi.domains/api/rpc/ \
     -H 'Content-Type: application/json' \
     -d '[{"jsonrpc":"1.0","id":1,"method":"getblockcount","params":[]},
          {"jsonrpc":"1.0","id":2,"method":"getdifficulty","params":[]}]'

# reply
[{"error":null,"id":1,"result":4269891},{"error":null,"id":2,"result":44218.07639246}]

3Look up a block

Blocks are found by hash. To get the hash of a block from its height, ask getblockhash. This one is a weekly lottery block, the one used in read a block:

curl -s https://services.divi.domains/api/rpc/ \
     -H 'Content-Type: application/json' \
     -d '{"jsonrpc":"1.0","id":"me","method":"getblockhash","params":[4263840]}'

# reply
{"error":null,"id":"me","result":"33bee78bfdf096ba783b1f9b8ee68330f8a7d78a19c8d7a824c58b451dc5b3b3"}

Now pass that hash to getblock:

curl -s https://services.divi.domains/api/rpc/ \
     -H 'Content-Type: application/json' \
     -d '{"jsonrpc":"1.0","id":"me","method":"getblock","params":["33bee78bfdf096ba783b1f9b8ee68330f8a7d78a19c8d7a824c58b451dc5b3b3"]}'

The reply is the same information Explorer 2.0 shows on the block page. Among other fields:

To see one of those transactions in full, ask getrawtransaction with the transaction ID and 1 to get it decoded. Read a transaction explains the fields.

curl -s https://services.divi.domains/api/rpc/ \
     -H 'Content-Type: application/json' \
     -d '{"jsonrpc":"1.0","id":"me","method":"getrawtransaction","params":["2d26ee0bc25ceafb9e890faac07e655dc75043b79f8a6aef4cd655db97e0cf0c",1]}'

4Look up an address

The address methods take an object with a list of addresses. Here is the testnet faucet's address, the same one used in look up an address:

curl -s https://services.divi.domains/api/testnet/rpc/ \
     -H 'Content-Type: application/json' \
     -d '{"jsonrpc":"1.0","id":"me","method":"getaddressbalance","params":[{"addresses":["yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4"]}]}'

# reply
{"error":null,"id":"me","result":{"balance":6402358980000,"received":14450358880000}}

Amounts here are in satoshis, the smallest unit: 100,000,000 satoshis make 1 DIVI. So that balance is 64,023.5898 DIVI, and the address has received 144,503.5888 DIVI in all. Divide by 100,000,000 to get DIVI.

Swap the method for getaddresstxids to get the list of every transaction that touched the address, oldest first. The faucet had 34 on the day we checked. getaddressutxos lists the coins it holds right now, and getaddressdeltas lists every change to its balance.

5Ready-made answers: CSV, summary, network

The Divi RPC service also has three plain web addresses that do the adding up for you. Open them in a browser or fetch them with curl; no JSON to send.

Full history as a spreadsheet

curl -s https://services.divi.domains/api/testnet/rpc/csv/yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4.csv

# first lines of the reply
Date,Type,Amount (DIVI),Other Address,TxID,Block Hash
2026-10-22 01:13:19,IN,0.09,xw5qqLhd1C4wEUQA25akTDsuzqraigU2dw,b5822723…,d89276c1…

One row per transaction, newest first, amounts in DIVI. It is the same file as the Export CSV button on Explorer 2.0's address page. Export an address's history explains each column.

Totals for one address

curl -s https://services.divi.domains/api/testnet/rpc/summary/yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4.json

This adds up the CSV rows. The reply for the faucet on the day we checked, amounts in satoshis:

• transactions: 34 rows in the CSV
• stakes: 10 staking rewards won
• rewards: 166000000000, which is 1,660 DIVI earned from staking
• net_deposits: 6236358980000, which is 62,363.5898 DIVI: money in minus money out
• balance: 6402358980000, which is 64,023.5898 DIVI: deposits plus rewards
• first_stake: 2026-06-03, UTC
• last_stake: 2026-10-17, UTC
• stakes_30d: 3 stakes in the last 30 days
• rewards_30d: 49800000000, which is 498 DIVI in the last 30 days

The whole network

curl -s https://services.divi.domains/api/rpc/network.json

Two numbers you cannot get from a single RPC call: how many DIVI are staking across the network, and the typical reward for one stake. On mainnet the reply said about 2.55 billion DIVI staking and a median reward of 41500000000 satoshis, which is 415 DIVI. The method field explains how they are estimated. Estimate your stakes uses them.

6The classic explorer's API

The classic explorer at /explorer/ has its own API. Each question is a web address, and the answer is a bare number or a JSON object. Its API page lists them all. It covers mainnet only.

curl -s https://services.divi.domains/explorer/api/getblockcount
4269891

curl -s 'https://services.divi.domains/explorer/api/getblockhash?index=4263840'
33bee78bfdf096ba783b1f9b8ee68330f8a7d78a19c8d7a824c58b451dc5b3b3

curl -s https://services.divi.domains/explorer/ext/getmoneysupply
4801319732.574765

Calls under /api/ pass straight to its node. Calls under /ext/ come from the explorer's own database and are where the useful extras live:

7chainz's API

chainz, run by CryptoID, has a small query API for Divi mainnet. Put the question after ?q=:

curl -s 'https://chainz.cryptoid.info/divi/api.dws?q=getblockcount'
4269894

curl -s 'https://chainz.cryptoid.info/divi/api.dws?q=getdifficulty'
45506.96404921

curl -s 'https://chainz.cryptoid.info/divi/api.dws?q=totalcoins'
4801321807.57708930

curl -s 'https://chainz.cryptoid.info/divi/api.dws?q=getblockhash&height=4263840'
"33bee78bfdf096ba783b1f9b8ee68330f8a7d78a19c8d7a824c58b451dc5b3b3"

For an address, use q=getbalance&a=<address> or q=getreceivedbyaddress&a=<address>. Both answer in DIVI.

The block hash matches the other two services exactly. The block count and supply differ by a few blocks because the three answers were fetched a few minutes apart.

8Which one to use

When two answers differ, check the height each one was at first, then vault coins, then chainz's delay. If you want to program against the RPC service properly, with Python and JavaScript and every error code, read talk to a Divi node from Python and JavaScript. To try methods by clicking rather than typing, use the RPC playground.

If something goes wrong

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