Local Explorer Instance Configuration Tool

WHAT IT DOES

Local Explorer Instance Configuration Tool generates environment variable configurations and Docker Compose service fragments for local block explorer instances. You provide your chain's RPC URL, chain ID, chain name, explorer type (Blockscout, Otterscan/Etherscan clone, or custom), and optional database and extra environment settings. The tool generates a complete configuration file with all required environment variables, plus a Docker Compose service fragment that you can integrate into your local chain stack. The configuration includes chain-specific settings, indexer options, security keys, and feature flags tailored to the selected explorer type. This saves hours of manually researching and configuring block explorers for local development environments, letting you focus on building your protocol rather than wrestling with infrastructure.

HOW TO USE

Select your explorer type from the dropdown. Enter your chain name (e.g., "Local Testnet"), chain ID (e.g., "1337"), RPC URL (e.g., "http://localhost:8545"), and the port you want the explorer to run on. Optionally add database configuration variables (key=value per line) and any extra environment variables your explorer requires. Click "Generate Explorer Configuration." The tool builds a complete environment configuration file with all required variables, displays a summary of the generated settings, and shows the configuration file as a preview. If you're using Docker, the tool also provides a compose service fragment you can add to your docker-compose.yml. Use the copy buttons to copy the config file or compose fragment to your clipboard.

THE REAL MECHANISM

The tool uses a pure JavaScript template engine that operates entirely client-side. It selects a configuration template based on the explorer type: Blockscout requires extensive environment variables including database URLs, RPC endpoints, chain IDs, security keys, and multiple indexer feature flags; Otterscan (Etherscan clone) requires a simpler set including RPC URL, chain ID, and chain name; custom explorers allow arbitrary environment variable configuration. The tool constructs the environment variable map, merges user-provided database and extra settings, and generates a formatted .env file. For Docker users, the tool also generates a service fragment with the correct image, port mapping, and environment variable references. All processing is done in the browser—no data is sent to external servers.

WHAT IT CANNOT SEE

This tool cannot start or stop explorer instances—it only generates configuration files. It cannot detect if the explorer service is actually running or if the database is properly initialized. It cannot validate that the generated configuration will work with the user's specific environment, operating system, or Docker setup. It cannot generate configurations for non-EVM explorers. It cannot deploy the explorer automatically—you must run docker-compose or start the service yourself. It cannot handle database migrations, schema creation, or setup tasks. The tool does not verify that the RPC URL is reachable or that the chain ID matches the actual chain.

PLEASE NOTE

Local Explorer Instance Configuration Tool works for any EVM-compatible local chain and does not require a blockchain connection to function, though the network selector is provided for context. It is a configuration tool for developers, not an execution tool. It reads data only and does not send any information to external servers. The tool is free to use and does not require authentication. For best results, ensure your local chain is running and accessible before starting the explorer.