Skip to main content

Parameters

string
required
Account address (base-58 encoded)
object

Response

array
Array of signature information objects
string
Transaction signature (base-58 encoded)
number
Slot in which the transaction was processed
object
Error if transaction failed, null if transaction succeeded
string
Memo associated with the transaction
number
Unix timestamp of when the transaction was processed
string
Transaction confirmation status

Code Examples

Basic Request

Request with Config

Using web3.js

Notes

  1. Returns confirmed transaction signatures for an address
  2. Results are returned in reverse chronological order
  3. Pagination can be achieved using the before parameter
  4. The response is immediate as it reads from the current state
  5. Different commitment levels can be specified

Best Practices

  1. Use appropriate limit based on your needs
  2. Implement pagination for large result sets
  3. Cache results when appropriate to reduce RPC load
  4. Consider using websocket subscription for real-time updates
  5. Handle network errors and retry when appropriate

Common Errors

Use Cases

  1. Transaction History
  2. Transaction Monitoring
  3. Transaction Analysis