fbda1b4beb
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
3.0 KiB
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 — 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 — 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):
./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:
- Fetches deployer balance from RPC (
eth_getBalanceorcast balance). - Fetches deployer balance from Blockscout (
GET /api/v2/addresses/{address}). - 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
- Chain 138: Use explorer.d-bis.org for balances, transactions, and contracts.
- Other chains (Ethereum, etc.): Use blockscan.com (or etherscan.io) to check balances on those chains.
- Reference: Canonical contract addresses and deployer are in CONTRACT_ADDRESSES_REFERENCE.