1Who runs what
| Explorer 2.0 | chainz | |
|---|---|---|
| Address | services.divi.domains/explorer2/ | chainz.cryptoid.info/divi/ |
| Run by | Divi Services, on its own Divi nodes | CryptoID, a third party that indexes hundreds of coins |
| Networks | Mainnet, and testnet at /testnet/explorer2/ | Mainnet only |
| Calls the coin | Divi | "Divicoin", the coin's older name |
| Costs | Free, no ads, no key | Free, ad-supported; the API is limited to one call every 10 seconds unless you have a key |
Neither one is the chain. Both read the same blocks from a Divi node and present them. That is why the next section is short.
2What they agree on
Block heights, block hashes, transaction ids, amounts and timestamps are facts of the chain, and both sites show them the same. Block 4,263,840 has hash 33bee78b… and two transactions on both. If they ever disagree on a block, one of them is behind or has briefly followed a losing fork; wait a few minutes and reload.
They present the same facts differently. Explorer 2.0 shows a block's size as 0.92 KB where chainz says 0.9 kB; Explorer 2.0 gives the time in your local zone where chainz gives UTC. Same block.
3Why a balance can differ
Balances are not written in the chain; each explorer adds them up itself, and the two use different rules. The important case is staking vaults. Coins in a vault sit on a special two-key script, one key for the staking node and one for the owner. Explorer 2.0 asks the node for both the ordinary coins and the vault coins of an address and shows them as separate cards (Balance, Vault Balance, Total Balance). chainz does not know about vault scripts, so it attributes those coins to neither key.
The owner address of one large vault shows a Vault Balance of about 3.5 million DIVI on Explorer 2.0 and a Balance of 0 on chainz, with no transactions at all. Neither site is lying: chainz is answering "coins on a plain address" and Explorer 2.0 is answering "coins this owner controls". For any address that stakes through a vault, trust Explorer 2.0's figure.
Two smaller differences. chainz's own documentation says an address balance "can be delayed by up to 6 hours" on its API without a key, while Explorer 2.0 asks a node at the moment you load the page. And on the chainz block page, the lottery pot and reward are shown as coins "Created" by the block, so a lottery block reads "Created 504,415 DIVI", whereas Explorer 2.0 shows only the transaction outputs and lets you add them up. The two statements describe the same coins.
4Only on Explorer 2.0
- Vault figures: Vault Balance, Net Deposited and Rewards Earned on an address page. Look up an address.
- Staking Intelligence tab: return to date, yield over the last 30 days, how often to expect a stake and what each one pays, and a value in your currency.
- Exports: a CSV button on every address, plus CSV with prices, CoinTracker and OFX files by URL. Export an address history.
- Testnet: the same explorer for the test chain, where the faucet gives you coins to try things with.
- Mempool page: transactions waiting to be included, at /explorer2/mempool.
- Live block viewer: on the same site, /zmq/ (and /testnet/zmq/ for testnet) shows each new block and transaction the moment the node announces it. How it works.
- Raw data: every block and transaction card flips over to show the node's JSON, with a copy button.
- Open: the public RPC service returns the same data the explorer uses, so anything you read on a page you can also read from a script.
5Only on chainz
- Rich List: the top 1,000 addresses by balance and a wealth-distribution chart, from the front page. Remember the vault caveat above: vault coins are missing from it.
- Orphans: a list of blocks that lost a tie and were dropped from the chain, which Explorer 2.0 does not keep.
- Tags: some addresses carry a label such as an exchange's name, and the search box searches tags too ("Search address, block, transaction, tag...").
- Years of history in one place: chainz has indexed Divi since 2018 and is the explorer most old forum posts and support threads link to.
- Independence: it is run by someone other than Divi. When you want a second opinion on a transaction or a balance from a source Divi does not control, this is it.
- A simple query API:
api.dws?q=getblockcount,getdifficulty,getbalance&a=…,getreceivedbyaddress,totalcoins. One call per 10 seconds, by its own rules. Query the chain shows both APIs.
6Which to open
| You want to | Open |
|---|---|
| Check whether a payment arrived | Either. Both show the transaction within a minute. |
| Read a staking wallet's balance or rewards | Explorer 2.0. chainz cannot see vault coins. |
| Download your history for taxes | Explorer 2.0, CSV button. |
| See the largest holders | chainz Rich List (minus vaults). |
| Verify something independently of Divi | chainz. |
| Try things with coins that are not real | Explorer 2.0 on testnet. |
| Follow a link from a 2019 forum post | It will be chainz; the same block or transaction is on Explorer 2.0 by pasting the hash into search. |
| Pull numbers into a script | Explorer 2.0's RPC service for anything; chainz's API for a single balance or the block count. |
7The third one: the classic explorer
Divi Services also still runs the older explorer at /explorer/, built on the open-source eIquidus software. It has its own rich list, a masternode list, a "movement" page of large transactions, and a network page, and its block pages take a hash rather than a height. Unlike chainz, it does count vault coins toward the owner: for the large vault owner in section 3 it gives about 3.52 million DIVI, the same as Explorer 2.0, though as one plain balance rather than separate vault cards. It stays up because old links point at it; for anything new, start with Explorer 2.0.
If something goes wrong
| You see | What it means |
|---|---|
| chainz shows 0 for an address you know has coins | The coins are in a staking vault. Open the address on Explorer 2.0 and read Vault Balance. |
| chainz has no testnet | Correct; its testnet address redirects away. Use /testnet/explorer2/. |
| chainz API returns nothing or an error page | Wait 10 seconds between calls; it refuses faster ones. |
| Different confirmation counts | One site's node is a block or two behind. Both climb by one a minute; the difference is not a problem. |
| An address looks different on the two sites | A vault output: Explorer 2.0 shows both keys, chainz shows the script a different way. The transaction id is the same. |
Still stuck? Ask the Divi chatbot, or see all tutorials.