eth_getBlockTransactionCountByHash — Elysium JSON-RPC
Return the transaction count of a block.
https://triport.io/rpc/elysium- Network
- Elysium mainnet (chain ID 99901)
- Scope
- elysium:rpc
- Auth
- X-API-Key: $TRIPORT_API_KEY
- Rate limit
- elysium_read_rpc - 5 / 10 / 25 / 40 / 40 RPS sustained (Free / Basic / Pro / Business / Enterprise; BE5, 2026-11-08); Limits
Endpoint and plans: Elysium RPC endpoint.
eth_getBlockTransactionCountByHash — return the transaction count of a block. Elysium is an Arbitrum Orbit L2 (chain ID 99901) that pays gas in HYPE; the signature and response shape come from the Elysium OpenRPC contract.
The number of transactions in a block selected by hash.
Parameters
JSON-RPC params is a positional array.
blockHashHashrequiredResponse
Measured 2026-11-08 on Elysium mainnet; captured values in a reconstructed JSON-RPC envelope, not a captured Triport response.
On Elysium
The count includes the Nitro system transaction. Every Elysium block starts with an internal ArbOS transaction of type 0x6a sent from 0x00000000000000000000000000000000000a4b05, so a block with two user transactions reports 0x3, which is exactly what the capture for hash 0xc919…8046 returned.
Subtract one if you want user activity only, or check the type of index 0 before you do. The count is how you bound a loop over eth_getTransactionByBlockHashAndIndex: indices run from 0x0 to count minus one.
With blocks arriving roughly every tenth of a second, many Elysium blocks contain only the system transaction. A count of 0x1 is a normal, quiet block — useful as a cheap filter before fetching full block bodies when you scan for activity.
Errors
See Elysium errors. Inspect the code and message together.
| Code | Meaning | Action |
|---|---|---|
| -32601 | Method unavailable | Check the documented method set. A method outside it is rejected earlier with HTTP 403 method_unknown. |
| -32602 | Invalid parameters | Correct the request. |
| -32005 | Request limit exceeded | Arrives with HTTP 429: back off and honor Retry-After; see Limits. |
| -32000 | Upstream unavailable | Retry reads with bounded backoff. |
HTTP 429 rate_limited | Plan RPS exceeded (plain HTTP error, not JSON-RPC) | Honor Retry-After; see Limits. |
Examples
const response = await fetch("https://triport.io/rpc/elysium", {
method: "POST",
headers: { "X-API-Key": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
body: JSON.stringify({"jsonrpc":"2.0","id":1,"method":"eth_getBlockTransactionCountByHash","params":["0xc919128f94468931868392eaaad656f740d799155c8c8359158a9f5bb1a68046"]}),
});
const payload = await response.json();Notes
- The result is the view of the healthy node that answered; adjacent calls are not pinned to one node.
- For transaction submission, see eth_sendRawTransaction (live). The Triport contract excludes
net_listening,net_peerCount,txpool_*,debug_*andtrace_*: they are rejected with HTTP 403method_unknown; see unsupported methods.