POSTGet Transactions In Slot
https://web3.nodit.io/v1/solana/mainnet/blockchain/getTransactionsInSlotRetrieves the list of transactions included in a specific slot.
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 slot to query. You can enter one of the following formats:
- slot height: Enter the slot number as a decimal string.
- slot tag: Use "earliest" or "latest" to specify the first slot or the latest slot.
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.
Parameter specifying whether to include the instructions field in the response.
- instructions is a field that contains the list of instructions in the transaction.
- When this parameter is set to true, instructions are included in the response.
- instructions are not provided for failed transactions (status "failed").
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 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 list of all signatures included in the transaction. There may be two or more in a multisig or versioned transaction.
Example: 5XXN7L7cMGYTvckcaNeTXxhJgxeT1JTa9auwa2yXCFR1NXzwXrXNAWx4SaAw48S5186VzvXiXVEsWJu1WFR5AAmg
A field representing the list of instructions included in the transaction. This field is only included in the response when the withInstructions parameter is set to true.
Instructions are not provided for failed transactions (status "failed").
Field indicating the index of the instruction within the transaction. (0-based)
Example: 0
Field indicating the index of an inner (sub) instruction generated by CPI or similar.
Example: 0
Field indicating the order in which the instruction was executed within the transaction.
Example: 0
Field indicating the ID of the program that executed the instruction. Base58-encoded.
Example: 11111111111111111111111111111111
Field indicating the list of public keys of the accounts used by the instruction. Each public key is Base58-encoded.
Example: DsTrM688cmzj7jkC8Nw6B7ngYhCqDqqMGtgHQhKCBYm,VdhaA49Uy2Vb8h4RzxcsfdnjNPbbvNTBCowUU32k6Wi
Field indicating the instruction data. Base58-encoded.
Example: 3Bxs4HjPduGCo42T
Field indicating the stack depth of the instruction.
Example: 1
A field representing the list of log messages left by programs during transaction execution.
Example: Program 11111111111111111111111111111111 invoke [1],Program 11111111111111111111111111111111 success
A field representing the number of accounts that must sign the transaction. (numRequiredSignatures)
Example: 1
A field representing the number of readonly accounts among the signing accounts. (numReadonlySignedAccounts)
Example: 0
A field representing the number of readonly accounts among the non-signing accounts. (numReadonlyUnsignedAccounts)
Example: 3
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 recent blockhash referenced by the transaction. It is used for replay prevention and validity verification.
Example: mfcyqEXB3DnHXki6KjjmZck6YjmZLvpAByy2fj4nh6B
A field representing the version of the transaction. It has one of the values "legacy", "0", or "1".
Example: legacy
A field representing the compute budget configuration set on the transaction. It is provided only for SIMD-0385 v1 transactions and is not included in the response for legacy and v0 transactions. Each sub-field can be null, and null and 0 have different meanings. If the transaction does not set the corresponding item, null is returned.
A field representing the total priority fee set on the transaction, in lamports. It has a value within the u64 range and is returned as a string to avoid loss of precision. SetComputeUnitPrice on legacy and v0 transactions is denominated in micro-lamports per compute unit, so its unit differs from this field. In addition, the compute unit price of legacy and v0 transactions is not a transaction field and can only be obtained by decoding the instruction data.
Example: 100000
A field representing the compute unit limit set on the transaction. It has a value within the u32 range.
Example: 200000
A field representing the total size limit of the account data loaded by the transaction, in bytes. It has a value within the u32 range.
Example: 65536
A field representing the size of the heap memory used for dynamic allocation while the program runs inside the VM, in bytes. It has a value within the u32 range and is a multiple of 1KiB between 32KiB and 256KiB.
Example: 32768
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