/solscan/transactions

POST /api/solscan/transactions

Price: 1 credit

Get a Solana transaction's full details by its signature

How to use it

Get the full details of a Solana transaction by its signature. Returns the slot, block time, fee and priority fee, compute units, success/failed status, confirmation status, version, signers, the programs and accounts involved, SOL and token balance changes, the parsed instructions, the token transfers, and the program log messages.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tx string required — Transaction signature (base58) (examples: "32WxZsge1VJRxhian7P1TmpvZyJGmrVW1C1L56n9WHrdMy61fa5pKTBMkHau7V2W13NfgWx6dwrHkn1tboNpzunG")

Response

• @type string (default: "SolscanTransaction")
• signature string required
• slot integer nullable
• block_time integer nullable
• fee integer nullable
• priority_fee integer nullable
• compute_units integer nullable
• status string nullable
• tx_status string nullable
• version string nullable
• signers array (default: [])
• programs array (default: [])
• accounts array (default: [])
• tags array (default: [])
• sol_balance_changes array (default: [])
  • @type string (default: "SolscanSolBalanceChange")
  • address string required
  • pre_balance integer nullable
  • post_balance integer nullable
  • change_amount integer nullable
• token_balance_changes array (default: [])
  • @type string (default: "SolscanTokenBalanceChange")
  • address string nullable
  • owner string nullable
  • token_address string nullable
  • decimals integer nullable
  • pre_balance number nullable
  • post_balance number nullable
  • change_amount number nullable
  • change_type string nullable
• transfers array (default: [])
  • @type string (default: "SolscanTransferLeg")
  • source string nullable
  • source_owner string nullable
  • destination string nullable
  • destination_owner string nullable
  • token_address string nullable
  • decimals integer nullable
  • amount number nullable
  • transfer_type string nullable
• instructions array (default: [])
  • @type string (default: "SolscanInstruction")
  • index integer nullable
  • type string nullable
  • program string nullable
  • program_id string nullable
• log_messages array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Transaction not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.