Polygon zkEVM method that returns the number of transactions in a block specified by block number or tag. This information can be useful for analytics purposes.
Get you own node endpoint today
Start for free and get your app to production levels immediately. No credit card required.
You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
-
quantity or tag
— the integer of a block encoded as hexadecimal or the string with:-
latest
— the most recent block in the blockchain and the current state of the blockchain at the most recent block -
earliest
— the earliest available or genesis block -
pending
—the pending state and transactions block. This is the current state of transactions that have been broadcast to the network but have not yet been included in a block.See the default block parameter.
-
Response
quantity
— an integer value representing how many transactions are included in the block.
eth_getBlockTransactionCountByNumber
code examples
eth_getBlockTransactionCountByNumber
code examplesconst { Web3 } = require("web3");
const NODE_URL = "CHAINSTACK_NODE_URL";
const web3 = new Web3(NODE_URL);
async function getTransactionsCount(blockId) {
const count = await web3.eth.getBlockTransactionCount(blockId)
console.log(count);
}
getTransactionsCount('latest')
const ethers = require('ethers');
const NODE_URL = "CHAINSTACK_NODE_URL";
const provider = new ethers.JsonRpcProvider(NODE_URL);
const getTransactionsCount = async (blockId) => {
const count = await provider.send("eth_getBlockTransactionCountByNumber", [blockId]);
console.log(count);
};
getTransactionsCount('latest')
from web3 import Web3
node_url = "CHAINSTACK_NODE_URL"
web3 = Web3(Web3.HTTPProvider(node_url))
print (web3.eth.get_block_transaction_count(37278959)) # A hex value starting with "0x" is accepted as well.
Use case
eth_getBlockTransactionCountByNumber
can be used to analyze how many transactions are included on the Polygon zkEVM blockchain in a certain period. For instance, on average, a new block is generated on the zkEVM mainnet every 3 seconds, resulting in approximately 1,200 blocks per hour. Using a Web3 library, one can inspect the past 1,00 blocks starting from the latest block and use eth_getBlockTransactionCountByNumber
to find the number of transactions in each block to sum them.
Try the eth_getBlockTransactionCountByNumber
RPC method yourself
eth_getBlockTransactionCountByNumber
RPC method yourself