# Instructions Failed Table

| 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 failed instructions. You can:

* Identify the block context using `BLOCK_SLOT`, `TIMESTAMP`, `DATETIME, BLOCK_HASH`, and `BLOCK_HEIGHT`.
* Determine transaction order with `TRANSACTION_INDEX` and `TRANSACTION_ID`.
* Examine signer details through `SIGNER` and `SIGNERS`.
* Trace the instruction’s execution sequence via `INSTRUCTION_INDEX` and `INNER_INSTRUCTION_INDEX`.
* Understand the core details of the instruction with `PARSED`, `TYPE`, `PROGRAM`, and `PROGRAM_ID`.
* Review the involved accounts using `ACCOUNTS` and the encoded input data via DATA.
* Assess execution depth with `STACK_HEIGHT`.
* Determine if the instruction involves a transfer using `IS_TRANSFER`.
* Evaluate data recency with `DATE_CREATED` and `DATE_UPDATED`.

For example, you might query `DATETIME`, `PROGRAM_ID`, and `STACK_HEIGHT` to pinpoint where a failure occurred and better understand its context.
