RPC method

eth_getTransactionByHash on Tempo

Supported on SwiftNodes

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

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

0x2 EIP-1559	1 (100%)

Fields beyond Ethereum's

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

A real Tempo transaction

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

{
  "type": "0x2",
  "chainId": "0x1079",
  "nonce": "0x8d2b",
  "gas": "0xbcf01",
  "maxFeePerGas": "0x684ee180",
  "maxPriorityFeePerGas": "0x3b9aca00",
  "to": "0x334cc71f818324f3932ab9d41285450373b84cdc",
  "value": "0x0",
  "accessList": [],
  "input": "0xe9ae5c5300000000…(516 bytes)",
  "r": "0x4199c45aa33d6aa6fd18c3878f9c5bff314b492f820b39429af7ba7cb5582e70",
  "s": "0x73bb77a87760f5837ba31a54a6d5efdd614afbde2b7522caf031acd85dcdbab4",
  "yParity": "0x1",
  "v": "0x1",
  "hash": "0xc6cc445a5851e3d314a8f43c45be418e4c8fd24d863014b3ee99c51045174eee",
  "blockHash": "0x267e24d0d61867d34b7d805f5b08961d38b62772e9fe7ed53a755f6695a6be97",
  "blockNumber": "0x29ea319",
  "transactionIndex": "0x0",
  "from": "0xf080385c4d3e08859cfb26b379d3752b7e51395a",
  "gasPrice": "0x5f5e1000",
  "blockTimestamp": "0x6ace2ae7"
}

Example request

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

import { createPublicClient, http } from "viem";

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

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

Other methods on Tempo

eth_getTransactionByHash on other chains

Frequently asked questions

Does Tempo support eth_getTransactionByHash?

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

Which transaction types does Tempo use?

In five recent blocks: 1 × 0x2 (EIP-1559).

Why does eth_getTransactionByHash return null on Tempo?

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.

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

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