curl --request POST \
--url https://nd-995-911-243.p2pify.com/afb8312f3710a5bc469f4c87cad3a2e4 \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "zks_L1BatchNumber",
"params": []
}'
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"batchNumber": 123
}
}
curl --request POST \
--url https://nd-995-911-243.p2pify.com/afb8312f3710a5bc469f4c87cad3a2e4 \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "zks_L1BatchNumber",
"params": []
}'
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"batchNumber": 123
}
}
none
result
— the latest L1 batch number, returned as a hexadecimal string. This number increments with each new batch processed on the L1 network, providing a sequential identifier that can be used to track processing progress and batch-related activities.zks_L1BatchNumber
could be used to obtain the most recent batch number. This can be particularly useful for applications that need to display the current processing state of the zkSync network or to analyze transaction throughput over time.Successful response
The response is of type object
.
Was this page helpful?