RPC method

eth_getTransactionByHash on Cronos

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getTransactionByHash on Cronos through the same endpoint customers use, and is re-measured weekly.

What eth_getTransactionByHash does

Returns a transaction by its hash: sender, recipient, value, input data, gas fields and signature, plus the block it was included in. It returns null for a hash the node does not know, and a transaction still in the mempool has a null blockNumber.

Transaction types on Cronos

Types of the 8 transactions in five consecutive blocks when we measured. Decoders that reject unknown types will fail on Cronos if any of these is missing from their list.

0x0 legacy	4 (50%)
0x2 EIP-1559	4 (50%)

A real Cronos transaction

A type 0x0 transaction from one of the latest blocks, as our endpoint returned it (long hex values shortened).

{
  "blockHash": "0x56d19ca3dbf3a862d553c02c2a76ffb7ffc6fbf9ae726cb29385bd7ca251c5ca",
  "blockNumber": "0x5f0cdf5",
  "from": "0x295bb023fe8378b16df327343b5e3136cfa4f29b",
  "gas": "0x3e37c",
  "gasPrice": "0x6ae51f4bfc",
  "hash": "0x8305d43964040aa7a089bc444127495a7de5b435df58bde8fb1ba0dacfb3a5c4",
  "input": "0x27ee31696e486f2d…(164 bytes)",
  "nonce": "0x1722",
  "to": "0x7f8946b257ad9a8fa55704120957901741a3346c",
  "transactionIndex": "0x0",
  "value": "0x0",
  "type": "0x0",
  "chainId": "0x19",
  "v": "0x56",
  "r": "0x46ff0c7e905cd889d36274ae23c851e29949ab6094afc86280af3e314b9c1afa",
  "s": "0x31cfd8c6d5e401fdef23f30d377aaee30559fd35a4d32098569817724250501e"
}

Example request

curl -s https://rpc.swiftnodes.io/rpc/cronos?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionByHash","params":["0x8305d43964040aa7a089bc444127495a7de5b435df58bde8fb1ba0dacfb3a5c4"]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/cronos?key=YOUR_API_KEY"),
});

const tx = await client.getTransaction({ hash: "0x8305d43964040aa7a089bc444127495a7de5b435df58bde8fb1ba0dacfb3a5c4" });
if (tx.blockNumber === null) console.log("still pending");
console.log(tx.type, tx.from, tx.to, tx.value);

Other methods on Cronos

eth_getTransactionByHash on other chains

Frequently asked questions

Does Cronos support eth_getTransactionByHash?

Yes. eth_getTransactionByHash answered on the SwiftNodes Cronos endpoint when our weekly probe called it through the customer path (2026-10-13).

Which transaction types does Cronos use?

In five recent blocks: 4 × 0x0 (legacy), 4 × 0x2 (EIP-1559).

Why does eth_getTransactionByHash return null on Cronos?

The node does not know the hash: it was never broadcast, it was dropped from the mempool, or it was sent to another chain. Check the hash and the chain ID before retrying.

Cronos endpoints, live block height and WebSocket status are on the Cronos RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.