Skip to content

Solana method

getTransaction

Returns a confirmed transaction by signature, with its metadata.

moderateModerate: reads state or executes code, but over a bounded range.Primary specification (opens in a new tab)

How each provider handles it

3 providers

Provider support for getTransaction on Solana
ProviderStatusSuccessMedian
Solana FoundationSupported100.0%18 ms
PublicNodeSupported100.0%34 ms
TatumFailing0.0%—

Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.

Over time

Median latency per hour. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.

Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it. 1 provider is not plotted: they returned no successful response in this window, so they have no latency.

What it does

Everything about one transaction: the instructions, the accounts it touched, the compute units it consumed, its log output, and the balance changes it caused.

This is how an application confirms what a transaction actually did, and how an explorer renders it.

Parameters

signaturestringrequired
Transaction signature, base-58.
configObjectoptional
encoding, commitment, maxSupportedTransactionVersion.

Returns

Object | null.

Try it

Runnable as written, against a keyless public endpoint. Nothing here needs an API key.

Request

curl -s https://api.mainnet-beta.solana.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getTransaction","params":["5Nx8kQ2vRt7mYw3pL9dF...",{"encoding":"json","maxSupportedTransactionVersion":0}]}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getTransaction",
  "params": [
    "5Nx8kQ2vRt7mYw3pL9dF...",
    { "encoding": "json", "maxSupportedTransactionVersion": 0 }
  ]
}

Response

{
  "jsonrpc": "2.0",
  "result": {
    "slot": 372145830,
    "blockTime": 1755168000,
    "meta": {
      "err": null,
      "fee": 5000,
      "computeUnitsConsumed": 1401,
      "preBalances": [1000000000, 2039280],
      "postBalances": [999995000, 2039280]
    }
  },
  "id": 1
}

Things that bite

  • meta.err is null for success. A failed transaction is still recorded on chain and still charged a fee.
  • Without maxSupportedTransactionVersion, versioned transactions error rather than returning.

Why it is measured

The signature is discovered by a separate preparation call whose cost is excluded from the timing, so the measurement is transaction lookup and nothing else.

Called every 600 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.

24h window · generated 2026-10-08 19:46:52 UTC · 3 providers