POST
/
4ab982aa70a7baead515ffdb5915df3f
eth_getTransactionCount
curl --request POST \
  --url https://fantom-mainnet.core.chainstack.com/4ab982aa70a7baead515ffdb5915df3f \
  --header 'Content-Type: application/json' \
  --data '{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "eth_getTransactionCount",
  "params": [
    "0x18443ddbc5cd7Fb2F07551b54A37254F06819464",
    "latest"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": {}
}
Fantom API method that returns the number of transactions sent from an address at the selected block. This value is also called nonce; it is an important piece of information, especially to ensure that a transaction is not sent twice.
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

  • address— the address to retrieve the transaction count.
  • 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 an instance of severe propagation latency.
    • finalized — the block accepted as canonical by more than 2/3 of the validators. A chain reorganization is extremely unlikely, and it would require at least 1/3 of the staked amount to be burned.
    • earliest — the earliest available or genesis block.
    • pending — the pending state and transactions block. 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 and How The Merge Impacts Ethereum’s Application Layer.

​
Response

  • quantity — an integer value identifying the number of transactions sent from an address at the specified block.

​
eth_getTransactionCount code examples

const { Web3 } = require("web3");
const NODE_URL = "CHAINSTACK_NODE_URL";
const web3 = new Web3(NODE_URL);

async function getTransactionsCount(address, blockId) {
  const count = await web3.eth.getTransactionCount(address, blockId)
  console.log(count);
}

getTransactionsCount("0x18443ddbc5cd7Fb2F07551b54A37254F06819464", 'latest')

​
Use case

One of the most common use cases for eth_getTransactionCountis to create the transaction object built in a script designed to send a transaction. The nonce field is required, and it is retrieved using the eth_getTransactionCount method.

Body

application/json
​
id
integer
default:1
​
jsonrpc
string
default:2.0
​
method
string
default:eth_getTransactionCount
​
params
string[]

The address to check

Response

200 - application/json

The address nonce

​
jsonrpc
string
​
id
integer
​
result
object