Network coverage
One screening call resolves across seven networks. Tron and Solana are indexed natively rather than inferred from EVM heuristics.
| Network | Family and indexer |
|---|---|
| Ethereum | EVM, chain id 1 · Blockscout REST |
| BNB Chain | EVM, chain id 56 · JSON-RPC |
| Polygon | EVM, chain id 137 · JSON-RPC |
| Arbitrum | EVM, chain id 42161 · Blockscout REST |
| Base | EVM, chain id 8453 · Blockscout REST |
| Tron | Tron VM · TronGrid |
| Solana | Solana · Public RPC |
| Bitcoin | UTXO · Esplora REST |
Address formats
Format detection is shape-based. A 0x-prefixed 40-character hex string is treated as EVM; a base58 string beginning with T and 34 characters long is Tron; other base58 strings of 32 to 44 characters are Solana. Tron is tested before Solana because both use base58 and only Tron has a mandatory prefix and fixed length.
Where the network is ambiguous and none is selected, the EVM chains are probed in turn, starting with Ethereum. Transaction hashes are rejected with a prompt to enter one of the addresses involved instead.
Depth
- Keyless tier: balances and transfer counts on every network, plus counterparty resolution wherever a Blockscout instance is available.
- Solana public RPC is heavily rate-limited, so screening caps itself at a small number of calls and marks the result degraded rather than hanging.
- With an indexer key configured, counterparty resolution extends to all five EVM chains and the per-address transfer cap is lifted.
Bridges
Transfers that cross between networks are followed where the bridge counterparty is itself attributable. An unattributable bridge hop terminates that branch of the graph and is counted as unattributed exposure, not as clean flow.
Text last revised 12 Aug 2026