RPC method

eth_getTransactionByHash on Abstract

Supported on SwiftNodes

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

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

0x71 zkSync EIP-712	2 (100%)

A real Abstract transaction

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

{
  "blockHash": "0x65f9673094a4c3b0edb8a0cf0f841afe48da65736341dba4772929be547b5c54",
  "blockNumber": "0x537d964",
  "chainId": "0xab5",
  "from": "0x567fb9f73b1aba16477aa7bb1e246a4d7de8b25a",
  "gas": "0x30d400",
  "gasPrice": "0x2b275d0",
  "hash": "0x73e84b932f4ba4efd6462c54c8767fbdcd16a6058692b528bdf6730c73f38fe2",
  "input": "0x0b48ca6600000000…(452 bytes)",
  "maxFeePerGas": "0x2b275d0",
  "maxPriorityFeePerGas": "0x0",
  "nonce": "0x14",
  "r": "0xf1ebc217be67564af6244b8b3d782a8a370a2ccd742ab80d5d62136f9953d674",
  "s": "0x101d1136ed69d7bea99450d01979f07b89c15f517173436ecf8524186223a3ff",
  "to": "0x268031de8363401d61b6a256bea009bb57277619",
  "transactionIndex": "0x0",
  "type": "0x71",
  "v": "0x1",
  "value": "0x0",
  "yParity": "0x1"
}

Example request

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

import { createPublicClient, http } from "viem";

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

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

Other methods on Abstract

eth_blockNumberSupported
eth_chainIdSupported
eth_getBalanceSupported
eth_getBlockByNumberSupported
eth_getTransactionReceiptSupported
eth_callSupported
eth_estimateGasNot measured
eth_gasPriceSupported
eth_maxPriorityFeePerGasSupported
eth_sendRawTransactionSupported
eth_getTransactionCountSupported
eth_getCodeSupported
eth_subscribeSupported
eth_getLogsSupported
eth_getBlockReceiptsSupported
eth_feeHistorySupported
eth_getProofNot available
eth_createAccessListNot available
debug_traceCallSupported
trace_blockNot available
trace_transactionNot available

eth_getTransactionByHash on other chains

Frequently asked questions

Does Abstract support eth_getTransactionByHash?

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

Which transaction types does Abstract use?

In five recent blocks: 2 × 0x71 (zkSync EIP-712).

Why does eth_getTransactionByHash return null on Abstract?

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.

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

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