eth_blockNumber - zkSync
Example code for the eth_blockNumber JSON-RPC method. Сomplete guide on how to use eth_blockNumber JSON-RPC in GetBlock.io Web3 documentation.
Returns the number of the most recent L2 block on zkSync Era. With ~1 second block times, this is the standard way to poll for new blocks. Note: L2 blocks are grouped into L1 batches — use zks_L1BatchNumber for batch-level tracking.
Parameters
None
Request Example
curl --location --request POST 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
"jsonrpc": "2.0",
"method": "eth_blockNumber",
"params": [],
"id": "getblock.io"
}'import axios from 'axios';
const data = JSON.stringify({
"jsonrpc": "2.0",
"method": "eth_blockNumber",
"params": [],
"id": "getblock.io"
});
const config = {
method: 'post',
url: 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/',
headers: {
'Content-Type': 'application/json'
},
data: data
};
axios(config)
.then(response => console.log(JSON.stringify(response.data, null, 2)))
.catch(error => console.log(error));Response Example
{
"jsonrpc": "2.0",
"id": "getblock.io",
"result": "0x2249b7"
}Response Parameters
jsonrpc
string
JSON-RPC protocol version (2.0)
id
string
Request identifier echoed back
result
string
Latest L2 block number in hexadecimal
Use Cases
Polling for new L2 blocks in indexers and dApps
Determining the current chain tip before making other calls
Health-checking the RPC endpoint
Error Handling
403
Forbidden
Missing or invalid <ACCESS-TOKEN>
-32602
Invalid params
Request parameters are missing or malformed
429
Too Many Requests
Rate limit exceeded for your plan
SDK Integration
Last updated
Was this helpful?