Get you own node endpoint todayStart 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. A chain reorganization is to be expected.safe
—the block that received justification from the beacon chain. Although this block could be involved in a chain reorganization, it would necessitate either a coordinated attack by the majority of validators or severe propagation latency.finalized
—the block accepted as canonical by more than 2/3 of the validators. A chain reorganization is extremely unlikely, requiring burning at least 1/3 of the staked amount.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
Use case
eth_getBlockTransactionCountByNumber
can be used to analyze how many transactions are included on the Fantom blockchain in a certain period. For instance, on average, a new block is generated on the Fantom mainnet every 3 seconds, resulting in approximately 1,200 blocks per hour. Using a Web3 library, one can inspect the past 1,200 blocks starting from the latest block and use eth_getBlockTransactionCountByNumber
to find the number of transactions in each block to sum them.Body
application/json
Response
200 - application/json
The block transaction count information
The response is of type object
.