eth_getBlockTransactionCountByHash

eth_getBlockTransactionCountByHash returns a single integer: how many transactions are contained in the block whose hash you pass. It is the standard EVM read for "how big is this block" when you already hold the block hash (for example, from a logs entry, a receipt, or a prior eth_getBlockByHash call).

The count is returned as a hex-encoded quantity (e.g. "0x4d" = 77). If no block with the given hash exists on the canonical chain — an unknown hash, or a hash that was orphaned by a re-org — the method returns null rather than an error.

This is a light, low-cost read. In practice it is often redundant: a single eth_getBlockByNumber/eth_getBlockByHash already returns the transaction hashes, so their length gives you the same count without a second round-trip. Reach for this method when you specifically want the count and nothing else.

Polygon note: Polygon runs Bor consensus with ~2.1 s block time and no uncle blocks. A typical block carries ~50–150 transactions.

Positional params array, one element:

For a hash that is not found on the canonical chain:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": null
}

The result: null case above is not an error — it is the normal response for an unknown hash. The errors below are platform-level (auth, tier, rate limit) and share the standard JSON-RPC error envelope.

See errors.md for the full error envelope and field-by-field breakdown.

JavaScript (fetch)

const res = await fetch("https://api.triport.io/rpc/polygon", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "eth_getBlockTransactionCountByHash",
    params: ["0x8e38b4dbf6b11fcc3b9dee84fb7986e29ca0a02cecd8977c161ff7333329681e"],
  }),
});


const { result } = await res.json();
const count = result === null ? null : parseInt(result, 16);
console.log(count); // 77, or null if the block hash is unknown

TypeScript SDK (@triport/sdk)

import { TriportClient } from "@triport/sdk";


const client = new TriportClient({ apiKey: process.env.TRIPORT_API_KEY });


const result = await client.polygon.call<string | null>(
  "eth_getBlockTransactionCountByHash",
  ["0x8e38b4dbf6b11fcc3b9dee84fb7986e29ca0a02cecd8977c161ff7333329681e"],
);


const count = result === null ? null : parseInt(result, 16);
console.log(count);

Python (triport-sdk)

import os
from triport_sdk import TriportClient


client = TriportClient(api_key=os.environ["TRIPORT_API_KEY"])


result = client.polygon.call(
    "eth_getBlockTransactionCountByHash",
    ["0x8e38b4dbf6b11fcc3b9dee84fb7986e29ca0a02cecd8977c161ff7333329681e"],
)


count = None if result is None else int(result, 16)
print(count)

• null vs error: an unknown or orphaned block hash returns result: null, not a JSON-RPC error. Always handle null explicitly before parsing the hex count.
• Decode the result: the count is a hex quantity string — convert with parseInt(result, 16) (JS/TS) or int(result, 16) (Python).
• Re-org safety: because Polygon blocks can be re-orged out (Bor finality is ~2–3 epochs), a hash that resolved a moment ago can later return null. For confirmation logic, wait several blocks before trusting a hash.
• Related methods: eth_getBlockTransactionCountByNumber is the same read by block number; eth_getBlockByHash returns the full block (whose transaction list length gives the same count in one call).