ENVs
The app instance can be customized by passing variables to the Node.js environment at runtime.- Deprecated variables are available here.
- ENV list is also available in the frontend docs repo.
Read before you run the app
Variables compulsoriness
Please note that in the tables below, the “Compulsoriness” column indicates whether the variable is required for starting up the application, except for the “App Features” section. All features are optional by definition; therefore, the “Compulsoriness” column indicates whether a certain variable is required or optional only within the context of that feature, not for the entire application.Disclaimer about using variables
Please be aware that all environment variables prefixed withNEXT_PUBLIC_ will be exposed to the browser. So any user can obtain its values. Make sure that for all 3rd-party services keys (e.g., Auth0, WalletConnect, etc.) in the services administration panel you have created a whitelist of allowed origins and have added your app domain into it. That will help you prevent using your key by unauthorized app, if someone gets its value.
Note about escaping variables values
All json-like values should be single-quoted. If it contains a hash (#) or a dollar-sign ($) the whole value should be wrapped in single quotes as well (see dotenv readme for the reference)
Scroll horizontally to see all values in the variables tables.
Table of contents
- App configuration
- Blockchain parameters
- API configuration
- UI configuration
- App features
- My account
- Gas tracker
- Advanced filter
- Address verification in “My account”
- Blockchain interaction (writing to contract, etc.)
- Banner ads
- Text ads
- Beacon chain
- User operations
- Rollup chain
- Export data to CSV file
- Google analytics
- Mixpanel analytics
- GrowthBook feature flagging and A/B testing
- GraphQL API documentation
- REST API documentation
- Marketplace
- Solidity to UML diagrams
- Blockchain statistics
- Web3 wallet integration (add token or network to the wallet)
- Transaction interpretation
- Verified tokens info
- Name service integration
- Metadata service integration
- Public tag submission
- Data availability
- Bridged tokens
- Safe address tags
- Address profile API
- Address XStar XHS score
- SUAVE chain
- Celo chain
- Ton Application Chain (TAC)
- MetaSuites extension
- Validators list
- Sentry error monitoring
- Rollbar error monitoring
- OpenTelemetry
- DeFi dropdown
- Multichain balance button
- Get gas button
- Save on gas with GasHawk
- Rewards service API
- DEX pools
- 3rd party services configuration
App configuration
Blockchain parameters
Note! TheNEXT_PUBLIC_NETWORK_CURRENCY variables represent the blockchain’s native token used for paying transaction fees. NEXT_PUBLIC_NETWORK_SECONDARY_COIN variables refer to tokens like protocol-specific tokens (e.g., OP token on Optimism chain) or governance tokens (e.g., GNO on Gnosis chain).
API configuration
UI configuration
Homepage
Hero banner configuration properties
Note Here, all values are arrays of up to two strings. The first string represents the value for the light color mode, and the second string represents the value for the dark color mode. If the array contains only one string, it will be used for both color modes.Navigation
Featured network configuration properties
Footer
The app version shown in the footer is derived from build-time ENV variables
NEXT_PUBLIC_GIT_TAG and NEXT_PUBLIC_GIT_COMMIT_SHA and cannot be overwritten at run-time.
Footer links configuration properties
Favicon
By default, the app has generic favicon. You can override this behavior by providing the following variable. Hence, the favicon assets bundle will be generated at the container start time and will be used instead of default one.Meta
Settings for meta tags, OG tags and SEOViews
Block views
Block fields list
Address views
Address views list
Transaction views
Transaction fields list
Transaction additional fields list
Token views
NFT views
NFT marketplace properties
Note URL templates should contain placeholders of NFT hash (
{hash}) and NFT id ({id}). This placeholders will be substituted with particular values for every collection or instance.
Misc
Network explorer configuration properties
Note If a path template contains
:id or :id_lowercase, it will be replaced with the entity-id in its original case or lowercased respectively. If neither parameter is present, the entity-id will be appended to the end of the path in lowercase. For example, with baseUrl https://explorer.anyblock.tools:
- Path
{"tx":"/ethereum/poa/core/tx/:id/details"}and entity-id0x123...AbCresults inhttps://explorer.anyblock.tools/ethereum/poa/core/tx/0x123...AbC/details - Path
{"tx":"/ethereum/poa/core/tx/:id_lowercase/details"}and entity-id0x123...AbCresults inhttps://explorer.anyblock.tools/ethereum/poa/core/tx/0x123...abc/details - Path
{"tx":"/ethereum/poa/core/tx"}and entity-id0x123...AbCresults inhttps://explorer.anyblock.tools/ethereum/poa/core/tx/0x123...abc
Contract code IDE configuration properties
Font family configuration properties
App features
Note The variables which are marked as required should be passed as described in order to enable the particular feature, but they are not required in the entire app context.My account
Gas tracker
This feature is enabled by default. To switch it off passNEXT_PUBLIC_GAS_TRACKER_ENABLED=false.
Advanced filter
This feature is enabled by default. To switch it off passNEXT_PUBLIC_ADVANCED_FILTER_ENABLED=false.
Address verification in “My account”
Note all ENV variables required for My account feature should be passed alongside the following ones:Blockchain interaction (writing to contract, etc.)
Banner ads
Ads are enabled by default on all self-hosted instances. If you would like to disable ads, you can disable using the Autoscout hosted service.
Text ads
Ads are enabled by default on all self-hosted instances. If you would like to disable ads, you can disable using the Autoscout hosted service.
Beacon chain
User operations (ERC-4337)
Rollup chain
Parent chain configuration properties
Export data to CSV file
Google analytics
Mixpanel analytics
GrowthBook feature flagging and A/B testing
GraphQL API documentation
This feature is always enabled, but you can disable it by passingnone value to NEXT_PUBLIC_GRAPHIQL_TRANSACTION variable.
REST API documentation
This feature is always enabled, but you can disable it by passingnone value to NEXT_PUBLIC_API_SPEC_URL variable.
Marketplace
Marketplace app configuration properties
Solidity to UML diagrams
Blockchain statistics
Web3 wallet integration (add token or network to the wallet)
This feature is enabled by default with the[metamask] value. To switch it off pass NEXT_PUBLIC_WEB3_WALLETS=none.
Transaction interpretation
External transactions
Verified tokens info
Name service integration
This feature allows resolving blockchain addresses using human-readable domain names.Metadata service integration
This feature allows name tags and other public tags for addresses.Public tag submission
This feature allows you to submit an application with a public address tag.Data Availability
This feature enables views related to blob transactions (EIP-4844), such as the Blob Txns tab on the Transactions page and the Blob details page.Bridged tokens
This feature allows users to view tokens that have been bridged from other EVM chains. Additional tab “Bridged” will be added to the tokens page and the link to original token will be displayed on the token page.Bridged token chain configuration properties
Note The url to original token will be constructed as
<base_url>/<token_hash>, e.g https://eth.blockscout.com/token/<token_hash>
Token bridge configuration properties
SafeCore address tags
For the smart contract addresses which are Safe accounts public tag “Multisig: Safe” will be displayed in the address page header alongside to Safe logo.Address profile API
This feature allows the integration of an external API to fetch user info for addresses or contracts. When configured, if the API returns a username, a public tag with a custom link will be displayed in the address page header.Address profile API configuration properties
Address XStar XHS score
This feature allows the integration of an XStar API to fetch XHS score for addresses. When configured, if the API returns a score, a public tag with that score will be displayed in the address page header.SUAVE chain
For blockchains that implement SUAVE architecture additional fields will be shown on the transaction page (“Allowed peekers”, “Kettle”). Users also will be able to see the list of all transactions for a particular Kettle in the separate view.Celo chain
For blockchains that use the Celo platform. Note, that once the Celo mainnet becomes an L2 chain, these variables will be migrated to the Rollup configuration section.Ton Application Chain (TAC)
For Ton Application Chains, this feature enables additional views, such as a list of cross-chain operations and a detailed page for a specific cross-chain operation, as well as extra fields on the transaction page.MetaSuites extension
Enables MetaSuites browser extension to integrate with the app views.Validators list
The feature enables the Validators page which provides detailed information about the validators of the PoS chains.Sentry error monitoring
Note This feature is deprecated. All ENV variables will be removed in the future releases.Rollbar error monitoring
OpenTelemetry
OpenTelemetry SDK for Node.js app could be enabled by passingOTEL_SDK_ENABLED=true variable. Configure the OpenTelemetry Protocol Exporter by using the generic environment variables described in the OT docs. Note that this Next.js feature is currently experimental. The Docker image should be built with the NEXT_OPEN_TELEMETRY_ENABLED=true argument to enable it.