eth_getUncleCountByBlockHash — Elysium JSON-RPC
Return the uncle 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_getUncleCountByBlockHash — return the uncle 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.
Behaviour follows the standard EVM JSON-RPC semantics for this method.
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
On Elysium this always comes back as 0x0. The chain is an Arbitrum Orbit rollup ordered by one sequencer, and ordering by a sequencer leaves no competing blocks to be included later as ommers. The capture used the hash 0xc919…8046 and returned zero, as expected.
Selecting by hash is the right form when your pipeline already stores block hashes, for instance when replaying a saved block list or cross-checking an explorer export. If you only track numbers, the by-number variant is equivalent and avoids a hash lookup on your side.
For an Elysium-only consumer the call carries no information and can be skipped. Keep it only where shared multi-chain code expects the field. Pairing it with eth_getBlockByHash is the way to confirm that the hash belongs to a block the node actually knows.
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_getUncleCountByBlockHash","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.