Instructions Table

Stores information regarding the instructions of the transaction. This table provides all the details about the instructions.

Name	Type	Description
BLOCK_SLOT	FIXED	Slot number or identifier of the block.
TIMESTAMP	FIXED	Raw value of the time in Unix Epoch time (in UTC time zone), which is then converted to DATETIME column.
DATETIME	TIMESTAMP_NTZ	Timestamp of the transaction in UTC.
BLOCK_HASH	TEXT	The hash of a specific block in the chain.
BLOCK_HEIGHT	FIXED	Indicates the numerical position of a block within the blockchain.
TRANSACTION_INDEX	FIXED	The position or order of a transaction within a block of the blockchain.
TRANSACTION_ID	TEXT	Identifier for the transaction that includes the instruction being tested.
SIGNER	TEXT	n/a
SIGNERS	ARRAY	n/a
INSTRUCTION_INDEX	FIXED	Index of instruction within a transaction.
INNER_INSTRUCTION_INDEX	FIXED	Index of the inner instruction within a transaction.
PARSED	VARIANT	Core information regarding the instruction.
TYPE	TEXT	The type of instruction.
PROGRAM	TEXT	Program or smart contract associated with the instruction.
PROGRAM_ID	TEXT	The program ID of the instruction.
ACCOUNTS	VARIANT	The accounts involved in the instruction.
DATA	TEXT	The program input data encoded in a base-58 string.
STACK_HEIGHT	FIXED	The depth of the call stack during the execution of on-chain instructions.
IS_TRANSFER	BOOLEAN	Indicates whether the instruction involves a transfer.
IS_MINT	BOOLEAN	n/a
IS_BURN	BOOLEAN	n/a
DATE_CREATED	TIMESTAMP_NTZ	Indicates the date in which the data was loaded.
DATE_UPDATED	TIMESTAMP_NTZ	Indicates the date in which the data was updated.

🔍 Use these columns to gather comprehensive insights into transaction instructions. Analyze how individual instructions operate within a transaction, including which program was invoked, how many nested instructions occurred, and whether it involved actions like transfers, minting, or burning tokens, among others. You can:

• Identify the transaction context using BLOCK_SLOT, TIMESTAMP, DATETIME, BLOCK_HASH, BLOCK_HEIGHT, TRANSACTION_INDEX, and TRANSACTION_ID.

• Examine instruction details with SIGNER, SIGNERS, INSTRUCTION_INDEX, INNER_INSTRUCTION_INDEX, and PARSED.

• Understand the nature of the instruction by reviewing TYPE, PROGRAM, and PROGRAM_ID.

• Analyze the involved accounts and input data through ACCOUNTS and DATA.

• Evaluate the execution depth with STACK_HEIGHT.

• Determine if the instruction involves a transfer, minting, or burning using IS_TRANSFER, IS_MINT, and IS_BURN.

• Assess data recency with DATE_CREATED and DATE_UPDATED.

For example, you might query TRANSACTION_ID, INSTRUCTION_INDEX, and PROGRAM_ID to trace how a specific instruction was executed, as well as to capture additional critical details.