eth_getBlockTransactionCountByNumber — 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_getBlockTransactionCountByNumber — 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 number or tag.
Parameters
JSON-RPC params is a positional array.
blockNumberBlockTagrequiredlatest.Response
Measured 2026-11-08 on Elysium mainnet; captured values in a reconstructed JSON-RPC envelope, not a captured Triport response.
On Elysium
On Elysium the first transaction of every block is an ArbOS internal transaction (type 0x6a), so the smallest count you will see on a produced block is 0x1. The captured block 0x270775 reported 0x3: one system transaction and two signed transactions.
Use this method as a pre-filter when you sweep heights. Because Elysium produces about ten blocks per second, most blocks in a quiet period hold only the system entry; fetching the count first and skipping blocks with 0x1 saves the larger eth_getBlockByNumber call with full transactions.
Pass an explicit hex height when you need repeatable results. With latest the head changes between your count call and the following read, so the block you counted may not be the block you fetch next. Store the height you used together with the count.
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_getBlockTransactionCountByNumber","params":["0x270775"]}),
});
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.