JSON-RPC / ETH
eth_blockNumber
Source record for eth_blockNumber in xOneRS at commit 5af188d.
Status per client
Registered means a handler is present in the pinned source. It does not show that the method works end to end.
| Client | Status |
|---|---|
| xOneRS | Registered in source (crates/xone-rpc/src/eth.rs:22, cost class C0) |
| xOneC | Unavailable: no method list was extracted from a pinned source for this client. |
| xOnePy | Unavailable: no method list was extracted from a pinned source for this client. |
| xOneTS | Unavailable: no method list was extracted from a pinned source for this client. |
Access
Served when the listener API list names the namespace. The default HTTP list is eth, net and web3.
Parameters, response and errors
Not recorded. The pinned source does not state a schema for this method on this site; read the handler.
Request example
A read-only request with no parameters, as in the Ethereum JSON-RPC specification. Run it yourself against your own local node. This page sends nothing and records no response.
curl http://127.0.0.1:8545 \
-H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'Reviewed 14 November 2026. Repository guides hold the current implementation details.
KEEP THE CURIOSITY GOING
Another way in.
Edit this page on GitHub opens the data definition (data/site-pages.js). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.