RPC method

eth_getTransactionByHash on Katana

Supported on SwiftNodes

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

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

0x7e L1-to-L2 deposit (OP Stack)	5 (100%)

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 Katana transaction

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

{
  "blockHash": "0xb09df6e9fa3a5029622ec24137a8e968f98e4d677d469f54e9f77bff82136dce",
  "blockNumber": "0x2b0f99f",
  "blockTimestamp": "0x6ace27ba",
  "depositReceiptVersion": "0x1",
  "from": "0xdeaddeaddeaddeaddeaddeaddeaddeaddead0001",
  "gas": "0xf4240",
  "gasPrice": "0x0",
  "hash": "0x3a20eaf56b905e2af1e800567be789071bd4c7f94585afbd1daa60d6d8994716",
  "input": "0x3db6be2b00000558…(178 bytes)",
  "mint": "0x0",
  "nonce": "0x2b0f9bd",
  "r": "0x0",
  "s": "0x0",
  "sourceHash": "0x302bb6edf19927318b3f554345c8b8f9516223f0a838c1dc9f86dd85e7ccede0",
  "to": "0x4200000000000000000000000000000000000015",
  "transactionIndex": "0x0",
  "type": "0x7e",
  "v": "0x0",
  "value": "0x0",
  "yParity": "0x0"
}

Example request

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

import { createPublicClient, http } from "viem";

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

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

Other methods on Katana

eth_getTransactionByHash on other chains

Frequently asked questions

Does Katana support eth_getTransactionByHash?

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

Which transaction types does Katana use?

In five recent blocks: 5 × 0x7e (L1-to-L2 deposit (OP Stack)).

Why does eth_getTransactionByHash return null on Katana?

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.

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

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