RPC method

eth_getTransactionReceipt on Fraxtal

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_getTransactionReceipt on Fraxtal 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 Fraxtal: what we measured

Fields	22 (8 beyond the Ethereum set)
Receipt for an unknown hash	null
Size of the sample receipt	1.2 KB

Reading the fee and fields

Beyond the Ethereum fields, Fraxtal receipts carry 8 more. depositNonce: the nonce of an L1-to-L2 deposit transaction; depositReceiptVersion: the version of the deposit receipt format; l1GasPrice: the Ethereum base fee the L1 fee was priced with; l1GasUsed: the L1 gas the transaction's compressed data was estimated to use; l1Fee: the L1 data fee in wei, charged on top of gasUsed × effectiveGasPrice. Add it to get the real cost; l1BaseFeeScalar: the weight of Ethereum's execution base fee in the L1 fee (post-Ecotone formula); l1BlobBaseFee: the Ethereum blob base fee the L1 fee was priced with; l1BlobBaseFeeScalar: the weight of Ethereum's blob base fee in the L1 fee.

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 Fraxtal receipt

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

{
  "type": "0x7e",
  "status": "0x1",
  "cumulativeGasUsed": "0xbcef",
  "logs": "0 logs",
  "depositNonce": "0x2892488",
  "depositReceiptVersion": "0x1",
  "logsBloom": "0x0000000000000000…(256 bytes)",
  "transactionHash": "0xba4deddf9b66a1f392433bb07d1a28668d63dc5751991d74320a13eeba3aa313",
  "transactionIndex": "0x0",
  "blockHash": "0x400448d438d5338492fa85e53483f4671e579b32b7d59b7c1c4c4bbb05412230",
  "blockNumber": "0x2892485",
  "gasUsed": "0xbcef",
  "effectiveGasPrice": "0x0",
  "from": "0xdeaddeaddeaddeaddeaddeaddeaddeaddead0001",
  "to": "0x4200000000000000000000000000000000000015",
  "contractAddress": null,
  "l1GasPrice": "0x69f2a65",
  "l1GasUsed": "0x6cd",
  "l1Fee": "0x0",
  "l1BaseFeeScalar": "0x2faf080",
  "l1BlobBaseFee": "0x5d0f64",
  "l1BlobBaseFeeScalar": "0x0"
}

Example request

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

import { createPublicClient, http } from "viem";

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

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

// Total cost on Fraxtal: execution plus the L1 data fee
const execution = receipt.gasUsed * receipt.effectiveGasPrice;
const total = execution + (receipt.l1Fee ?? 0n);

Other methods on Fraxtal

eth_getTransactionReceipt on other chains

Frequently asked questions

Does Fraxtal support eth_getTransactionReceipt?

Yes. eth_getTransactionReceipt answered on the SwiftNodes Fraxtal 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 Fraxtal?

Add the receipt's l1Fee to gasUsed × effectiveGasPrice.

Why is the Fraxtal receipt null?

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

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

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