SwiftNodesSwiftNodes
Sign In
RPC method

eth_getTransactionByHash on Base

Supported on SwiftNodes

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

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

0x2 EIP-1559891 (92%)
0x0 legacy67 (7%)
0x7e L1-to-L2 deposit (OP Stack)5 (1%)
0x4 EIP-7702 set-code2 (0%)
0x1 EIP-2930 access list2 (0%)

Fields beyond Ethereum's

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

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

A real Base transaction

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

{
  "type": "0x2",
  "chainId": "0x2105",
  "nonce": "0x1eef",
  "gas": "0x43c64",
  "maxFeePerGas": "0x1769af3f",
  "maxPriorityFeePerGas": "0x1769af3f",
  "to": "0x51c72848c68a965f66fa7a88855f9f7784502a7f",
  "value": "0x0",
  "accessList": [],
  "input": "0x771d503f00000000…(289 bytes)",
  "r": "0xd53eafb85836c81f5ed189d84d39d395d26e6aa0759f0029e1288ce9c3e94e90",
  "s": "0x2dd379007143c70d1f3b1934f8b59936c03c63e3c6840f82b19ed69bd9fb52c7",
  "yParity": "0x0",
  "v": "0x0",
  "hash": "0xc7ba337968bbf59a2bb73741bd6a81af122473f970b13dd36387915d3a62e88a",
  "blockHash": "0x1d6457238217f618ca73e43e67b57e449ae44ed8d5a064c49139b4e79f745024",
  "blockNumber": "0x321e2e0",
  "transactionIndex": "0x1",
  "blockTimestamp": "0x6ace22a3",
  "from": "0x136126cd2de7ddeb1d82e0785451bbe346c9f22d",
  "gasPrice": "0x1769af3f"
}

Example request

curl -s https://rpc.swiftnodes.io/rpc/base?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionByHash","params":["0xc7ba337968bbf59a2bb73741bd6a81af122473f970b13dd36387915d3a62e88a"]}'
import { createPublicClient, http } from "viem";

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

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

Other methods on Base

eth_getTransactionByHash on other chains

Frequently asked questions

Does Base support eth_getTransactionByHash?

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

Which transaction types does Base use?

In five recent blocks: 5 × 0x7e (L1-to-L2 deposit (OP Stack)), 891 × 0x2 (EIP-1559), 67 × 0x0 (legacy), 2 × 0x4 (EIP-7702 set-code), 2 × 0x1 (EIP-2930 access list).

Why does eth_getTransactionByHash return null on Base?

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.

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

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