Freshest wallet data API. Zerion, Moralis, Allium, GoldRush, Mobula
Seconds between an organic transfer confirming on Base and the moment each wallet data API first returns it, measured continuously on real user transactions.
Every wallet app, portfolio tracker and exchange faces the same question. when a user receives funds, how long before the API my app is built on actually shows it. Providers advertise "real-time" and "sub-second indexing"; none publish comparable numbers. This benchmark measures it the only way that cannot be gamed. we pick a random, organic native transfer from the newest Base block, real user, different wallet every time, and poll each provider's wallet transactions API until the tx hash appears. Because the ground truth is a random real transaction there is no benchmark wallet a provider could special-case, and every measurement is publicly re-verifiable from the tx hash. Cohort. Zerion, Moralis, Allium, GoldRush (Covalent) and Mobula, all probed with the identical schedule from the same host. The timing context matters in 2026. Dune Sim is sunsetting and SimpleHash is gone, so teams are choosing a replacement wallet data API right now, and freshness is the spec sheet line that separates them.
Methodology
We measure the visibility lag of wallet data APIs. the time between an organic native transfer confirming on Base (T0 = the instant our own RPC observes the containing block) and the first poll at which each provider's wallet transactions endpoint returns that tx hash. One probe event per 10 minutes; each event uses a fresh random transaction from a fresh block, so wallets are cold and results include any lazy, on-demand indexing path a provider runs for never-before-queried addresses. Detection is parser-free (tx hash substring in the raw response), the poll schedule is front-loaded (1s to 120s, identical for every provider), and per-provider monthly quota guards keep the probe inside every free tier. An event a provider has not indexed within 120 seconds counts as missed, which feeds the reliability column, because an API that never shows the deposit is worse than a slow one.
Frequently asked
Which wallet data API shows new transactions fastest?
Per the live leaderboard above: Mobula at 1.5 s (p50 over 24h of organic Base transfers). The ranking re-sorts continuously as probe events land every 10 minutes. Check the miss-rate column too, a provider that occasionally never indexes a transfer is worse for a wallet app than one that is a second slower on median.
How is indexing freshness measured here?
The harness picks a random organic native transfer from the newest Base block, records T0 when its own RPC observes the block, then polls every provider's wallet transactions endpoint on an identical front-loaded schedule (1s to 120s) until the tx hash appears in the raw response. The lag is the first successful poll. Events a provider has not indexed within 120 seconds count as missed. The full harness is open source and each measurement can be re-verified from the public tx hash.
Why use random real transactions instead of a controlled test wallet?
Two reasons. First, integrity: a fixed benchmark wallet could be whitelisted or pre-warmed by a provider; a random real user's transfer, different every event, cannot. Second, realism: cold, never-before-queried addresses exercise any lazy indexing path a provider runs for new wallets, which is exactly what a new user experiences. The trade-off, disclosed in the methodology, is that continuously-queried warm wallets may see lower lags than reported here.
Does this benchmark cover more chains than Base?
Not yet. Base was chosen first for its high volume of plain native transfers (dense organic ground truth) and 2-second blocks. The harness is chain-agnostic and additional EVM chains join by adding an RPC endpoint, subject to each provider's free-tier quota budget. Chain coverage itself differs per provider and is part of what teams should evaluate.
Why does freshness matter when choosing a wallet API in 2026?
Because the market is consolidating. Dune Sim is sunsetting in August 2026 and SimpleHash shut down in 2025, so many teams are migrating to a new wallet data API right now. Providers advertise real-time indexing but publish no comparable numbers; deposit visibility lag is the difference between a user seeing their funds arrive and a support ticket. This page is the only continuously measured, provider-neutral comparison of that number.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/indexing-freshness