RPC method

eth_getTransactionByHash on Mode

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getTransactionByHash on Mode 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 Mode

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

0x2 EIP-1559	15 (75%)
0x7e L1-to-L2 deposit (OP Stack)	5 (25%)

Fields beyond Ethereum's

Type 0x7e (L1-to-L2 deposit (OP Stack)) transactions carry extra fields. depositReceiptVersion: the version of the deposit receipt format; mint: the amount of ETH minted on L2 by a deposit; sourceHash: the unique ID of an L1-to-L2 deposit, derived from its L1 origin.

Transactions include blockTimestamp, so you get the block time without a second call for the block.

A real Mode transaction

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

{
  "accessList": [],
  "blockHash": "0x229491daaadc0dc760556fdecbc027ab77971e5bde1e8d64693acaef8aac62ff",
  "blockNumber": "0x2bbd496",
  "blockTimestamp": "0x6ace28cb",
  "chainId": "0x868b",
  "from": "0x45a07f120b36bfeb602a3880fc1629a879ba487b",
  "gas": "0xb71b00",
  "gasPrice": "0xdc718",
  "hash": "0xbd8679150e4b6fe1f786ef9cda62145258e574dca05c91297d0be96fa0c61ce8",
  "input": "0x0200680000000bb8…(243 bytes)",
  "maxFeePerGas": "0x2c4c94",
  "maxPriorityFeePerGas": "0xdc61c",
  "nonce": "0x9ffdd",
  "r": "0x8b9abc416c2c24b4af5fa50a581563ebc126ffff0c8d5e2ddc59e72bc208c90c",
  "s": "0x2e6cf860434f91a1e99c49065b1330bd0de21a0d4a84b77eb4828b3fe1876514",
  "to": "0x3c68c5aeafaf22af5aa22708953c1536d8b02bdc",
  "transactionIndex": "0x1",
  "type": "0x2",
  "v": "0x1",
  "value": "0x0",
  "yParity": "0x1"
}

Example request

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

import { createPublicClient, http } from "viem";

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

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

Other methods on Mode

eth_getTransactionByHash on other chains

Frequently asked questions

Does Mode support eth_getTransactionByHash?

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

Which transaction types does Mode use?

In five recent blocks: 5 × 0x7e (L1-to-L2 deposit (OP Stack)), 15 × 0x2 (EIP-1559).

Why does eth_getTransactionByHash return null on Mode?

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.

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

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