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

Start building today!     

Contents

getConfirmedSignaturesForAddress2 RPC Method

This method is deprecated and will not be supported in future versions. For a similar method, you can use solana's getSignaturesForAddress RPC method.

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

Parameters:

  1. acc_add - string - The account address as base-58 encoded string
  2. object - (optional) The configuration object with the following fields:

    limit - integer - (optional) (default: 1,000) The maximum number of transaction signatures to return. The valid range is between 1 and 1,000

    before - string - (optional) A base58-encoded transaction signature. If provided, the method will only return signatures that occurred before the specified transaction

    until - string - (optional) A base58-encoded transaction signature. If provided, the method will only return signatures that occurred at or before the specified transaction

    Commitment - string - (optional) (default: finalized) The level of commitment required for the query. The options include:

    Finalized - string - The node will query the most recent block confirmed by the supermajority of the cluster as having reached maximum lockout, meaning the cluster has recognized this block as finalized

    Confirmed - string - The node will query the most recent block that has been voted on by the supermajority of the cluster

Returns:

  1. result - An array of transaction signature information, ordered from newest to oldest transaction:

    blockTime - The estimated production time, as Unix timestamp (seconds since the Unix epoch) of when transaction was processed. It's null if not available

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

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

    memo - The memo associated with the transaction and null if no memo is present

    signature - The base58-encoded signature of the transaction

    slot - The slot number in which the transaction was confirmed

Code Examples:

const web3 = require("@solana/web3.js");
(async () => {
  const publicKey = new web3.PublicKey(
    "Vote111111111111111111111111111111111111111"
  );
  const solana = new web3.Connection("http://sample-endpoint-name.network.quiknode.pro/token-goes-here/");
  console.log(await solana.getConfirmedSignaturesForAddress2(publicKey));
})();
Ready to get started? Create a free account