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
PublicNodeSupported99.9%32 ms
Solana FoundationSupported99.8%24 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 day. 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.

When it degraded

A degradation is a bucket where a provider fell away from ITS OWN median for this method over the window, not from the cohort's. A provider that is consistently slower than its peers is not degraded — it is slower, which the ranking already says. Buckets with fewer than 20 samples are skipped, because a claim about a provider cannot rest on a handful of calls, and adjacent bad buckets are merged so one outage reads as one incident.

Solana Foundation

  • median rose to 67ms from a typical 21ms

    latency · 2026-09-09 00:00Z → 2026-09-10 00:00Z

  • median rose to 43ms from a typical 21ms

    latency · 2026-09-13 00:00Z

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.

30d window · generated 2026-10-08 18:33:21 UTC · 3 providers