RPC method

eth_getTransactionByHash on Lisk

Supported on SwiftNodes

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

Types of the 5 transactions in five consecutive blocks when we measured. Decoders that reject unknown types will fail on Lisk 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. sourceHash: the unique ID of an L1-to-L2 deposit, derived from its L1 origin; mint: the amount of ETH minted on L2 by a deposit; depositReceiptVersion: the version of the deposit receipt format.

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

A real Lisk transaction

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

{
  "type": "0x7e",
  "sourceHash": "0x7f19de836d4babb47ac597033cc08019fe630cfd514d58cdb04135ed4e6f4bad",
  "from": "0xdeaddeaddeaddeaddeaddeaddeaddeaddead0001",
  "to": "0x4200000000000000000000000000000000000015",
  "mint": "0x0",
  "value": "0x0",
  "gas": "0xf4240",
  "input": "0x3db6be2b0001f237…(178 bytes)",
  "hash": "0x6b540c6cb4c8552e928a6288f0588655145fc6d828764ac17fa0e0a58da48369",
  "r": "0x0",
  "s": "0x0",
  "yParity": "0x0",
  "v": "0x0",
  "blockHash": "0xa985f2121701da99ee5b2d95df1150fafede171d94886c55e843b41898dc925a",
  "blockNumber": "0x24cbe48",
  "transactionIndex": "0x0",
  "blockTimestamp": "0x6ace2be7",
  "depositReceiptVersion": "0x1",
  "gasPrice": "0x0",
  "nonce": "0x24cbe68"
}

Example request

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

import { createPublicClient, http } from "viem";

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

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

Other methods on Lisk

eth_getTransactionByHash on other chains

Frequently asked questions

Does Lisk support eth_getTransactionByHash?

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

Which transaction types does Lisk use?

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

Why does eth_getTransactionByHash return null on Lisk?

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.

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

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