Ethereum method
eth_getTransactionCount
Returns how many transactions an address has sent — its nonce.
How each provider handles it
This method has not been measured in this window.
It is scheduled but no observation has landed yet.
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 acceptlatest, 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
pendingnonces 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.
6h window · generated 2026-08-24 16:32:46 UTC · 0 providers