Frontend Migration

🚗 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.

The new frontend includes generalized support for L2s including views for attributes such as Index, L1 Timestamp, Size, L1 tx hash, L1 block number, and Batch root, new UI features and enhancements like the DApp marketplace and advanced statistics, and a new micro services infrastructure.

There are several options when deploying the new frontend and migrating your instance. You can either deploy in an all-in-one container, or deploy the frontend separately and connect it to the backend for more flexibility. If you have a custom backend (have made significant changes to the indexer etc) please use option 3.

If you need help or would like Blockscout to assist with migration or hosting please reach out in our Discord.

1. All-in-one: This is an easier deployment process but less flexible. It will deploy everything within a single docker container. DO NOT use if you plan to host your frontend separately or want to make significant changes to the frontend.

2. Separate frontend: Deploy the frontend first, then connect it to the backend. This lets you make more front-end customizations, and gives you access to all images etc. Use this method to run a separate frontend instance.

3. Customized backend: If you've customized the indexer and don't want to override it, keep your previous backend customizations and only deploy the frontend container.