POSTGet Transaction Summaries By Account
https://web3.nodit.io/v1/solana/mainnet/blockchain/getTransactionSummariesByAccountRetrieves the list of transaction summaries associated with a specific account. A summary includes only the key fields from the full transaction details.
Parameter to specify the target chain for the query.
Parameter to specify the network of the target chain. Supported networks may vary depending on the chain.
Parameter specifying the account address to query. The account address must be entered as a 32–44 character Base58-encoded string.
Parameter for filtering only the transactions where the queried account address belongs to from or to.
Three options are available: from, to, and both. The default value is both.
- from: Returns transactions where the queried address is a signer or its balance decreased.
- to: Returns transactions where the balance of the queried address increased.
- both: Returns all transactions that match either the from or the to condition.
Parameter specifying the start point of the query. You can enter one of the following formats:
- slot height: Enter the slot number as a decimal string.
- slot tag: Use "earliest" to specify the first slot.
If none of the range parameters (fromSlot, toSlot, fromDate, toDate) are specified, data from the last 30 days is returned. To query the full history, set fromSlot to "earliest".
Notes:
- This field cannot be used together with fromDate and toDate.
- If only fromSlot is provided without toSlot, results are queried from that slot to the latest slot.
- toSlot value cannot be less than fromSlot value.
- If fromSlot and toSlot have the same value, only that slot is queried.
- "latest" cannot be entered for fromSlot.
Parameter specifying the end point of the query. You can enter one of the following formats:
- slot height: Enter the slot number as a decimal string.
- slot tag: Use "latest" to specify the latest slot.
If none of the range parameters (fromSlot, toSlot, fromDate, toDate) are specified, data from the last 30 days is returned. To query the full history, set fromSlot to "earliest".
Notes:
- This field cannot be used together with fromDate and toDate.
- If only toSlot is provided without fromSlot, results are queried from the first stored slot to that slot.
- toSlot value cannot be less than fromSlot value.
- If fromSlot and toSlot have the same value, only that slot is queried.
- "earliest" cannot be entered for toSlot.
Parameter specifying the start date of the query. The date must follow the ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) and include seconds.
If none of the range parameters (fromSlot, toSlot, fromDate, toDate) are specified, data from the last 30 days is returned.
Notes:
- This field cannot be used together with fromSlot and toSlot.
- If only fromDate is provided without toDate, results are queried from that date to the latest slot.
- fromDate must be equal to or earlier than toDate.
Parameter specifying the end date of the query. The date must follow the ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) and include seconds.
If none of the range parameters (fromSlot, toSlot, fromDate, toDate) are specified, data from the last 30 days is returned.
Notes:
- This field cannot be used together with fromSlot and toSlot.
- If only toDate is provided without fromDate, results are queried from the first stored slot to that date.
- toDate must be equal to or later than fromDate.
The page parameter specifies the data page to query. It accepts values up to 100; for pages exceeding 100, use the cursor pagination method.
The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.
rpp stands for results per page and specifies the page size. You can specify a number greater than 0 and up to 100.
The cursor parameter supports pagination and data navigation between pages. Provide the cursor value from the previous page in the next request to load the next page of data.
The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.
Parameter specifying whether to include the count field in the response. The count field indicates the total number of requested data items. When set to true, the count field is included and response speed may be slower.
Parameter specifying whether to include the balanceChanges field in the response.
- balanceChanges is a field that contains the balance changes of the Native token (SOL) and Token.
- Setting this parameter to true may slow down the response.
Field representing the page number specified in the page parameter. This field is only included in the response when a value greater than 0 is specified for the page parameter.
Field representing the number of results per page specified in the rpp parameter.
A field for cursor pagination. This value must be provided in the next request to load the next page of data.
Field representing the total count of requested data. This field is only included in the response when true is set for the withCount parameter.
A field representing the start of the query in date mode. Returned in ISO 8601 format.
Example: 2026-09-29T09:40:23.000Z
A field representing the end of the query in date mode. Returned in ISO 8601 format.
Example: 2026-10-29T09:40:21.000Z
A field representing the start slot number of the query in slot mode.
Example: 462000000
A field representing the end slot number of the query in slot mode.
Example: 462833902
A field representing the slot number in which the transaction is included. On Solana, a slot corresponds to the block unit of other chains.
Example: 235157119
A field representing the block height to which the slot is mapped.
Example: 214567890
A field representing the time the block (slot) was created, as a Unix timestamp (seconds).
Example: 1746479684
A field representing the order of the transaction within the same slot.
Example: 7
A field representing the representative signature of the transaction. It is usually the first signature and is Base58-encoded.
Example: 5XXN7L7cMGYTvckcaNeTXxhJgxeT1JTa9auwa2yXCFR1NXzwXrXNAWx4SaAw48S5186VzvXiXVEsWJu1WFR5AAmg
A field representing the Compute Units (CU) actually consumed by the transaction.
Example: 6842
A field representing the cost units of the transaction processing cost.
Example: 6842
A field representing the transaction fee in lamports. It may be charged regardless of success or failure.
Example: 5000
A field representing the version of the transaction. It has one of the values "legacy", "0", or "1".
Example: legacy
A field representing the list of account addresses that signed the transaction.
Example: 9vNYXEehFV8V1jxzjH7Sv3BBtsYZ92HPKYP1stgNGHJE
A field representing the processing status of the transaction. "success" is returned when processed normally, and "failed" is returned when it fails.
Example: success
A field representing the error summary string when the transaction fails. It is a human-readable conversion of the Solana TransactionError.
Example: custom program error: 0x1
A field representing the details of SOL and SPL token balance changes that occurred in the transaction. This field is only included in the response when the withBalanceChanges parameter is set to true.
A field representing the address of the program that caused the balance change. (e.g. System Program)
Example: 11111111111111111111111111111111
A field representing the address of the account (owner) where the balance change occurred.
Example: 9vNYXEehFV8V1jxzjH7Sv3BBtsYZ92HPKYP1stgNGHJE
A field representing the address of the SPL token account where the balance change occurred. For a SOL balance change, an empty string ("") is returned.
Example: 7YttLkHDoNj9wyDur5pM1ejNaAvT9X4e3n9mQqZp8y8o
A field representing the MintAddress of the SPL token subject to the balance change. For a SOL balance change, "So11111111111111111111111111111111111111111" is returned.
Example: So11111111111111111111111111111111111111112
A field representing the amount of the balance change. A negative value indicates an outflow, and a positive value indicates an inflow. For SOL, it is expressed in lamports.
Example: -5000
A field representing the balance immediately before the change. For SOL, it is expressed in lamports.
Example: 1000000000
A field representing the balance immediately after the change. For SOL, it is expressed in lamports.
Example: 999995000
A field representing the number of decimal places of the token. For SOL, it is 9.
Example: 6