RPC method

eth_getTransactionReceipt on Abstract

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getTransactionReceipt on Abstract through the same endpoint customers use, and is re-measured weekly.

What eth_getTransactionReceipt does

Returns the outcome of a mined transaction: status (1 success, 0 reverted), gas used, the effective gas price, the logs it emitted and any contract it created. It returns null until the transaction is in a block.

eth_getTransactionReceipt on Abstract: what we measured

Fields	17 (3 beyond the Ethereum set)
Receipt for an unknown hash	null
Size of the sample receipt	6.2 KB

Reading the fee and fields

Beyond the Ethereum fields, Abstract receipts carry 3 more. l1BatchNumber: the L1 batch that includes the block or transaction; l1BatchTxIndex: the transaction's position inside its L1 batch; l2ToL1Logs: messages from L2 to L1 emitted by the transaction.

A hash the node has not seen returns null, not an error, so poll until it is non-null (viem's waitForTransactionReceipt does this) and give up after a timeout.

A real Abstract receipt

As our endpoint returned it; logs collapsed to a count and long hex values shortened.

{
  "blockHash": "0x65f9673094a4c3b0edb8a0cf0f841afe48da65736341dba4772929be547b5c54",
  "blockNumber": "0x537d964",
  "contractAddress": null,
  "cumulativeGasUsed": "0x0",
  "effectiveGasPrice": "0x2b275d0",
  "from": "0x567fb9f73b1aba16477aa7bb1e246a4d7de8b25a",
  "gasUsed": "0x2406f",
  "l1BatchNumber": null,
  "l1BatchTxIndex": null,
  "l2ToL1Logs": [],
  "logs": "7 logs",
  "logsBloom": "0x0000000000044000…(256 bytes)",
  "status": "0x1",
  "to": "0x268031de8363401d61b6a256bea009bb57277619",
  "transactionHash": "0x73e84b932f4ba4efd6462c54c8767fbdcd16a6058692b528bdf6730c73f38fe2",
  "transactionIndex": "0x0",
  "type": "0x71"
}

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_getTransactionReceipt","params":["0x73e84b932f4ba4efd6462c54c8767fbdcd16a6058692b528bdf6730c73f38fe2"]}'

import { createPublicClient, http } from "viem";

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

const receipt = await client.waitForTransactionReceipt({ hash, timeout: 60_000 });
if (receipt.status !== "success") throw new Error("reverted");

const total = receipt.gasUsed * receipt.effectiveGasPrice;

Other methods on Abstract

eth_blockNumberSupported
eth_chainIdSupported
eth_getBalanceSupported
eth_getBlockByNumberSupported
eth_getTransactionByHashSupported
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_getTransactionReceipt on other chains

Frequently asked questions

Does Abstract support eth_getTransactionReceipt?

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

How do I get the total fee of a transaction on Abstract?

gasUsed × effectiveGasPrice from the receipt.

Why is the Abstract receipt null?

The transaction is not in a block yet, or the hash is unknown to the node. Keep polling with a timeout.

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.