Description

Token details (for example View on block explorer from the More menu) pass the asset chain id, but useBlockExplorer only used built-in / PopularList explorers, then fell back to Etherscan using the globally selected network. Chains such as Gnosis (0x64) can have a block explorer in NetworkController while the user stays on Ethereum; those URLs were ignored.

After the built-in / PopularList lookup, the hook now calls findBlockExplorerUrlForChain(currentChainId, networkConfigurations) so URLs match the token's chain.

• GitHub #26211
• TMCU-709

Changelog

CHANGELOG entry: Fixed token details opening Etherscan instead of the correct block explorer for tokens on custom or non–PopularList networks when another EVM network was selected.

Related issues

Fixes: #26211

Refs: https://consensyssoftware.atlassian.net/browse/TMCU-709

Manual testing steps

Feature: Token details block explorer

  Scenario: Custom network token opens correct explorer
    Given the wallet has a custom or non–PopularList EVM network with a block explorer (e.g. Gnosis)
    And the globally selected network is Ethereum Mainnet
    And the user opens token details for a token on the custom network

    When the user opens the More menu and taps View on block explorer

    Then the in-app browser opens the block explorer for the token's chain, not Etherscan

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.