BNB Smart Chain method
eth_getBalance
Returns an address's balance in wei at a given block.
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| BNB Chain | Supported | 100.0% | 18 ms |
| NodeReal | Supported | 100.0% | 19 ms |
| PublicNode | Supported | 100.0% | 24 ms |
| Blast API | Supported | 99.6% | 104 ms |
| 1RPConerpc | Rate limited | 4.5% | 1534 ms |
Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.
Over time
Median latency per day. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.
Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it.
When it degraded
A degradation is a bucket where a provider fell away from ITS OWN median for this method over the window, not from the cohort's. A provider that is consistently slower than its peers is not degraded — it is slower, which the ranking already says. Buckets with fewer than 20 samples are skipped, because a claim about a provider cannot rest on a handful of calls, and adjacent bad buckets are merged so one outage reads as one incident.
1RPC
median rose to 3813ms from a typical 1360ms
latency · 2026-10-03 00:00Z
What it does
A state read. The node looks the account up in the state trie at the requested block and returns its balance. Unlike the head methods, this touches the database, so its latency reflects how well the provider's storage layer is provisioned.
The block parameter matters more than it looks. Asking for `latest` reads the tip; asking for a block from last year requires an archive node, and most providers answer that with an error rather than a balance.
Parameters
addressDATA, 20 bytesrequired- The account to read.
blockQUANTITY | TAGrequired- A block number in hex, or one of
latest,earliest,pending,safe,finalized.Default: none — most clients acceptlatest, but the parameter is not optional in the specification and some providers reject the call without it
Returns
QUANTITY — the balance in wei, in hex.
Try it
Runnable as written, against a keyless public endpoint. Nothing here needs an API key.
Request
curl -s https://ethereum-rpc.publicnode.com \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x00000000219ab540356cBB839Cbe05303d7705Fa","latest"],"id":1}'As JSON-RPC
{
"jsonrpc": "2.0",
"method": "eth_getBalance",
"params": ["0x00000000219ab540356cBB839Cbe05303d7705Fa", "latest"],
"id": 1
}Response
{
"id": 1,
"jsonrpc": "2.0",
"result": "0x2a1b4ae7d4a4c8f5c1a0"
}Things that bite
- The example address is the beacon chain deposit contract, chosen because it is high-value, permanently active, and its balance is public — so the call is comparable between providers and reveals nothing about anyone.
- Wei, not ether. Dividing by 10^18 is the caller's job, and getting it wrong by three orders of magnitude is a rite of passage.
Why it is measured
It separates providers whose state database is warm from those serving reads off cold storage. Against eth_chainId — which touches no state — the difference is the cost of the lookup rather than the network path.
Called every 120 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.
7d window · generated 2026-10-08 18:19:04 UTC · 5 providers