# Explorer and Blockscan — Which Explorer for Which Chain

**Purpose:** Use the right explorer per chain: **explorer.d-bis.org** for Chain 138; **blockscan.com** (or etherscan.io) for balances and activity on other chains (Ethereum mainnet, etc.).

---

## Use Blockscan for other chains

**blockscan.com** is the right tool to **check balances and activity on Ethereum mainnet and other chains** that Blockscan supports. The same address can hold different balances on each chain.

| Chain | Explorer | Example (deployer address) |
|-------|----------|----------------------------|
| **Ethereum mainnet, etc.** | **https://blockscan.com** | [blockscan.com/address/0x4A666F96fC8764181194447A7dFdb7d471b301C8](https://blockscan.com/address/0x4A666F96fC8764181194447A7dFdb7d471b301C8) — use to check balances on mainnet and other supported chains |
| **Chain 138 (SMOM-DBIS-138)** | **https://explorer.d-bis.org** | [explorer.d-bis.org/address/0x4A666F96fC8764181194447A7dFdb7d471b301C8](https://explorer.d-bis.org/address/0x4A666F96fC8764181194447A7dFdb7d471b301C8) — use for Chain 138 only |

- **To check balances on other chains:** Use **blockscan.com** (or etherscan.io) and select the chain; same address, different chain = different balance.
- **To check balances on Chain 138:** Use **explorer.d-bis.org** only; Blockscan does not show Chain 138.

---

## Deployer / Admin address

- **Address:** `0x4A666F96fC8764181194447A7dFdb7d471b301C8`
- **Chain 138 (balance, txs, contracts):** https://explorer.d-bis.org/address/0x4A666F96fC8764181194447A7dFdb7d471b301C8
- **Other chains (e.g. Ethereum mainnet):** https://blockscan.com/address/0x4A666F96fC8764181194447A7dFdb7d471b301C8
- **RPC (Chain 138):** https://rpc-core.d-bis.org or http://192.168.11.211:8545

---

## Compare deployer balance: Blockscout vs RPC

To check that Blockscout’s index matches the current chain (e.g. after running a script that uses RPC), compare the deployer’s native balance from **Blockscout API** and from **RPC**:

**Script (from repo root):**
```bash
./scripts/verify/check-deployer-balance-blockscout-vs-rpc.sh
```

Optional args: `[RPC_URL] [EXPLORER_API_URL]`. Defaults: RPC = `RPC_URL_138` or `https://rpc-core.d-bis.org`, Explorer API = `https://explorer.d-bis.org/api/v2`.

The script:
1. Fetches deployer balance from **RPC** (`eth_getBalance` or `cast balance`).
2. Fetches deployer balance from **Blockscout** (`GET /api/v2/addresses/{address}`).
3. Prints both in wei and ETH and reports whether they match (diff ≤ 1 wei).

Run from a host that can reach both the Chain 138 RPC and the Blockscout API (explorer.d-bis.org). If Blockscout is behind, the script reports the difference so you can re-run after the indexer catches up.

---

## Summary

1. **Chain 138:** Use **explorer.d-bis.org** for balances, transactions, and contracts.
2. **Other chains (Ethereum, etc.):** Use **blockscan.com** (or etherscan.io) to check balances on those chains.
3. **Reference:** Canonical contract addresses and deployer are in [CONTRACT_ADDRESSES_REFERENCE](CONTRACT_ADDRESSES_REFERENCE.md).