Transaction Count (Nonce) of an Address on an EVM Chain

evmrpc/transaction-count

The nonce of an address at the newest block: how many transactions it has sent, with pending ones not counted (for a contract, how many contracts it has created). For an externally owned account with nothing in flight that is the nonce its next transaction must use; with transactions waiting in a node's pool it is too low. Read from public nodes that offer no SLA and can be slow, throttled or a block behind; a failing node is replaced by another operator's automatically. Served by Eden Engine; not an official product of any chain or node operator.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.

Data source

Public blockchains

On-chain data read from public blockchain nodes; no licence or credit is required. Served by Eden Engine; not an official product of any chain or node operator.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "evmrpc/transaction-count" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "evmrpc/transaction-count" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "evmrpc/transaction-count", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "evmrpc/transaction-count", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.0026

Updated: Oct 21, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "required": [
    "chain",
    "address"
  ],
  "properties": {
    "chain": {
      "enum": [
        "ethereum",
        "base",
        "arbitrum",
        "optimism",
        "bsc"
      ],
      "type": "string",
      "description": "chain slug; see evmrpc/chain-info for ids and names"
    },
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "A 20-byte account or contract address: 0x followed by 40 hex digits."
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "required": [
    "transaction_count"
  ],
  "properties": {
    "transaction_count": {
      "type": [
        "integer",
        "null"
      ],
      "description": "Transactions sent by the address up to the newest block (its nonce); pending ones not counted."
    },
    "transaction_count_hex": {
      "type": [
        "string",
        "null"
      ]
    }
  },
  "description": "The address's nonce at the newest block.",
  "additionalProperties": false
}