Solana method
getTransaction
Returns a confirmed transaction by signature, with its metadata.
How each provider handles it
This method has not been measured in this window.
It is scheduled but no observation has landed yet.
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.
configObjectoptionalencoding,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.errisnullfor 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-08-24 16:32:07 UTC · 0 providers