BNB Smart Chain method

eth_getTransactionCount

Returns how many transactions an address has sent — its nonce.

cheapCheap for a provider to serve — no state is read, or one key is.Primary specification

How each provider handles it

Provider support for eth_getTransactionCount on BSC
Provider	Status	Success	Median	Worst p95	Incidents	Samples
NodeReal	Supported	100.0%	20 ms	78 ms	none	34,006
BNB Chain	Supported	100.0%	19 ms	81 ms	none	68,484
PublicNode	Supported	99.9%	24 ms	110 ms	none	34,235
Blast API	Supported	99.2%	116 ms	991 ms	none	34,138
1RPConerpc	Rate limited	2.4%	2444 ms	7953 ms	none	17,719

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.

What it does

The nonce. Every transaction from an account must carry the next one in sequence, so anything that sends a transaction reads this first.

The block parameter is unusually consequential here. At `latest` it counts mined transactions only; at `pending` it includes ones sitting in that node's mempool. Using `latest` while a transaction is still pending produces a nonce that is already taken, and the replacement is rejected.

Parameters

addressDATA, 20 bytesrequired: The account.
blockQUANTITY | TAGrequired: A block number in hex, or one of latest, earliest, pending, safe, finalized.Default: none — most clients accept latest, but the parameter is not optional in the specification and some providers reject the call without it

Returns

QUANTITY — the transaction count 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_getTransactionCount","params":["0x28C6c06298d514Db089934071355E5743bf21d60","latest"],"id":1}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "method": "eth_getTransactionCount",
  "params": ["0x28C6c06298d514Db089934071355E5743bf21d60", "latest"],
  "id": 1
}

Response

{
  "id": 1,
  "jsonrpc": "2.0",
  "result": "0x1f4a2"
}

Things that bite

Mempools are per-node. Two providers will legitimately return different pending nonces for the same address at the same moment.

Why it is measured

It sits directly on the transaction-sending path, so its latency is felt by every user who presses confirm.

Called every 300 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.

30d window · generated 2026-10-08 18:19:03 UTC · 5 providers