Skip to main content

Parameters

string
required
Transaction signature (base-58 encoded)
object
Configuration object containing:
string
Commitment level (processed, confirmed, finalized)
string
Encoding for transaction data (base58, base64, jsonParsed)
number
Maximum transaction version to support

Response

object
Object containing:
number
The slot the transaction was processed in
object
object
object
number
Number of required signatures
number
Number of read-only signed accounts
number
Number of read-only unsigned accounts
array
Array of account public keys (base-58 encoded)
string
Recent blockhash used for transaction
array
Array of instruction objects containing:
string
Program ID (base-58 encoded)
array
Array of account indices
string
Instruction data (base-58 encoded)
array
Array of transaction signatures (base-58 encoded)
object
object
Error object if transaction failed
number
Fee paid for the transaction
array
Array of account balances before the transaction
array
Array of account balances after the transaction
array
Array of inner instruction objects
array
Array of log messages
array
Array of token balances before the transaction
array
Array of token balances after the transaction
array
Array of reward objects

Code Examples

Basic Request

Using web3.js

Notes

  1. Returns transaction details for a given signature
  2. The transaction must be confirmed to be returned
  3. The response includes detailed information about the transaction
  4. The transaction can be parsed in different encodings
  5. The transaction must be a valid signature

Best Practices

  1. Use appropriate commitment level based on your needs
  2. Cache results when appropriate to reduce RPC load
  3. Monitor for transaction status changes
  4. Consider using websocket subscription for real-time updates
  5. Handle network errors and retry when appropriate

Common Errors

Use Cases

  1. Transaction Analysis
  2. Transaction Monitoring
  3. Transaction Planning