Skip to main content
🚗 Autoscout is now available, providing a simple one-click explorer deployment with Blockscout’s optimized hosting infrastructure. Use it for early testing, modifications, and launching a full production-grade explorer. Get Started Now and have your explorer up-and-running in minutes.

Supported JSON RPC Clients

BlockScout currently supports Geth, Erigon, Nethermind, Reth, Besu, RSKj, Lotus, and Anvil JSON RPC clients. To define the JSON RPC node variant, it’s advised to define the ETHEREUM_JSONRPC_VARIANT environment variable*. Correct values include: *If the variable is not set, JSON RPC variant will be chosen based on CHAIN_TYPE variable according to the mapping https://github.com/blockscout/blockscout/blob/a2625803c831fb86e38ffe0e28d94bfd697914ce/apps/ethereum_jsonrpc/lib/ethereum_jsonrpc/variant.ex#L114-L120
BlockScout currently requires a full archive node in order to import every state change for every address on the target network.

Configs

Variables to connect to JSON RPC client

Geth

More information on Geth JSON-RPC is available here.
Tracing and pruning: By default, state for the last 128 blocks kept in memory. Most states are garbage collected. If you are running a block explorer or other service relying on transaction tracing without an archive node (—gcmode=archive), you need to trace within this window! Alternatively, specify the “reexec” tracer option to allow regenerating historical state; and ideally switch to chain tracing which amortizes overhead across all traced blocks.

Erigon

More information on Erigon configuration is available here.

Nethermind

More information on Nethermind configuration is available here.

Reth

More information on Reth configuration is available here.

RSKj

More information on RSKj configuration is available here.

Besu

More information on Besu configuration is available here.

Lotus

More information on Lotus configuration is available here.

OpenEthereum