AptosAptos Network's breakthrough technology and seamless user experience are now available on QuickNode.

Start building today!     


getSignatureStatuses RPC Method

The API credit value for this method is 1 . To learn more about API credits and each method's value, visit the API Credits page.


  1. tx signatures - string - An array of transaction signatures to confirm encoded as base-58 strings
  2. object - (optional) The configuration object with the following fields:

    searchTransactionHistory - boolean - (optional) (default: false) If true, the search includes the entire transaction history. If false, the search only includes recent transactions in the latest confirmed block


  1. result - An object with the following fields:

    context - The information about the current state of the program

    apiVersion - The version of the Solana RPC API to use

    slot - An integer representing the slot for which to retrieve the fee calculator

    value - A JSON object with the following fields:

    confirmationStatus - The transaction's cluster confirmation status. It can either be processed, confirmed, or finalized

    confirmations - The number of confirmations a transaction has received. If the transaction is finalized (i.e., confirmed at the highest level of commitment), the value will be null

    err - Error code if the transaction failed or null if the transaction succeeds

    slot - The slot number in which the transaction was confirmed

    status - The processing status of the transaction. It returns Ok if the transaction was successful and Err if the transaction failed with TransactionError

Code Examples:

const web3 = require("@solana/web3.js");
(async () => {
  const accountOne =
  const accountTwo =
  const solana = new web3.Connection("http://sample-endpoint-name.network.quiknode.pro/token-goes-here/");
    await solana.getSignatureStatuses([accountOne, accountTwo], {
      searchTransactionHistory: true,
Ready to get started? Create a free account