Optimizing multi-chain data fetching for an EVM wallet tracker without requiring wallet connection. How do you handle RPC and API latency?

Post original

the multicall3 suggestion isnt a clean swap for blockscout because of token discovery. multicall is great once you know which erc20s to read, but the hard part blockscout is doing for you is telling you which tokens an arbitrary address even holds per chain. go to raw rpc and youre back to maintaining a token list per network or scanning Transfer logs to find holdings, which is its own indexing job for read only balances id skip self indexing entirely and use a portfolio api that already does the multichain holding lookup in one call (alchemy portfolio, covalent, zerion, ankr all expose this). then cache per chain with stale-while-revalidate keyed on the latest block so first paint is instant and each chain refreshes on its own, which is the snapshot first thing others mentioned the arbitrum lag youre seeing is almost certainly the explorer indexer trailing the chain not your code. hit the arb rpc directly for the same address and compare, if rpc is current and blockscout isnt thats your answer