eth_getUncleCountByBlockNumber — Elysium JSON-RPC

Return the uncle count of a block.

POSThttps://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.

Terms on this page: Chain ID · JSON-RPC · Sequencer.

eth_getUncleCountByBlockNumber — 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.

blockNumberBlockTagrequired
Block number in hex, or a tag such as latest.

Response

Measured 2026-11-08 on Elysium mainnet; captured values in a reconstructed JSON-RPC envelope, not a captured Triport response.

On Elysium

Elysium has no uncles. Its blocks come from a single Nitro sequencer, so there is no proof-of-work race and no orphaned sibling that a later block could cite as an ommer. The measured answer for block 0x270775 is 0x0; a single-sequencer chain does not produce uncles at any height.

The method is served so that tooling written for Ethereum mainnet — explorers, generic indexers, block comparison scripts — runs against Elysium without a special case. In an indexer built only for Elysium you can drop this call entirely and keep the request inside your plan budget for something useful. A branch in your code that handles a non-zero count is unreachable on this chain.

A zero here says nothing else about the block: it does not prove the height exists or is final. Read the block itself with eth_getBlockByNumber when you need its contents.

Errors

See Elysium errors. Inspect the code and message together.

CodeMeaningAction
-32601Method unavailableCheck the documented method set. A method outside it is rejected earlier with HTTP 403 method_unknown.
-32602Invalid parametersCorrect the request.
-32005Request limit exceededArrives with HTTP 429: back off and honor Retry-After; see Limits.
-32000Upstream unavailableRetry reads with bounded backoff.
HTTP 429 rate_limitedPlan 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_getUncleCountByBlockNumber","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_* and trace_*: they are rejected with HTTP 403 method_unknown; see unsupported methods.