Local Explorer

Dome uses Blockscout as the optional local explorer for the EVM dev chain.

Start

Ensure Hardhat is running and reachable from Docker:

npx hardhat node --hostname 0.0.0.0 --port 8545

Deploy contracts, then start Blockscout:

bash scripts/base/deploy-local.sh
bash scripts/explorer/blockscout-local.sh up -d

Open http://localhost:5100

If Blockscout shows "Something went wrong", hard-refresh (Ctrl+Shift+R) so the browser picks up the updated API host config.

Or use the all-in-one dev script:

bash scripts/dev/up.sh --explorer

RPC from Docker

Blockscout's Hardhat profile uses:

http://host.docker.internal:8545

On Linux this is enabled via extra_hosts: host-gateway in the upstream Compose file.

If Hardhat binds only to 127.0.0.1, browser wallets may work via Next.js proxy but Docker cannot reach the chain. Always use --hostname 0.0.0.0 when running Blockscout locally.

Commands

# Status
bash scripts/explorer/blockscout-local.sh ps

# Stop
bash scripts/explorer/blockscout-local.sh down

# Different port
DOME_BLOCKSCOUT_PORT=5101 bash scripts/explorer/blockscout-local.sh up -d

# Reset Blockscout DB volumes
bash scripts/explorer/blockscout-local.sh down -v

The helper clones Blockscout's Docker Compose into .dome-local/blockscout, applies Dome overrides, and runs the hardhat-network.yml profile. ERC-4337 user-ops indexing is disabled for local Hardhat.

Troubleshooting

If the UI shows "Something went wrong" and Docker logs repeat connecting to shim / cleaning up dead shim, the backend is crash-looping:

bash scripts/explorer/blockscout-local.sh down -v
bash scripts/explorer/blockscout-local.sh up -d

Then open http://localhost:5100 again.

Start

RPC from Docker

Commands

Troubleshooting

On this page