> For the complete documentation index, see [llms.txt](https://glint-analytics.gitbook.io/glint-analytics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/priced-net-transfers-failed-table.md). # Priced Net Transfers Failed Table Records failed priced network transfers on the Solana blockchain, which can help identify transaction issues and potential network congestion. | 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. | | `TRANSACTION_INDEX` | `FIXED` | The position or order of a transaction within a block. | | `TRANSACTION_ID` | `TEXT` | Unique identifier assigned to each transaction within the blockchain. | | `INSTRUCTION_INDEX` | `FIXED` | Index of the instruction within a transaction. | | `INNER_INSTRUCTION_INDEX` | `FIXED` | Index of the inner instruction within a transaction. | | `TRANSFER_TYPE` | `TEXT` | This can be “IN” or “OUT.” Differentiates whether a token has moved into or out of a wallet. | | `ACCOUNT` | `TEXT` | The address of the wallet or the party in the transaction. | | `CP_ACCOUNT` | `TEXT` | The address of the counterparty, which could be another wallet, exchange, or smart contract. | | `TOKEN_ADDRESS` | `TEXT` | The address of the token. | | `NAME` | `TEXT` | The name of the token being searched. | | `SYMBOL` | `TEXT` | The symbol of the token being searched. | | `VALUE` | `REAL` | The curated quantity of the token. A negative value indicates the token is being sent out. A positive value indicates that a token is being received. | | `TOKEN_FEE` | `REAL` | The fee or royalties associated with the token account. | | `USD_VALUE` | `REAL` | The curated value of the token, proceed in USD. | | `USD_TOKEN_FEE` | `REAL` | The token fee, priced in USD value. | | `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 priced network transfers on the Solana blockchain. Analyze failed transfers—including both incoming and outgoing token movements with USD-converted values—to diagnose transaction issues and potential network congestion. The table helps you understand the context of each failure by providing details about the block and transaction, the specific instruction indices, the transfer direction, and the participating accounts, among others. You can: * Identify the block and transaction context using `BLOCK_SLOT`, `TIMESTAMP`, `DATETIME`, `TRANSACTION_INDEX`, and `TRANSACTION_ID`. * Pinpoint the specific instruction using `INSTRUCTION_INDEX` and `INNER_INSTRUCTION_INDEX`. * Determine the transfer direction with `TRANSFER_TYPE`. * Investigate the involved accounts via `ACCOUNT` and `CP_ACCOUNT`. * Retrieve token characteristics using `TOKEN_ADDRESS`, `NAME`, and `SYMBOL`. * Analyze the transfer amounts and fee details with `VALUE`, `TOKEN_FEE`, and `USD_VALUE`including `USD_TOKEN_FEE`. * Monitor data recency with `DATE_CREATED` and `DATE_UPDATED`. For example, you might query `VALUE`, `TOKEN_FEE`, and `USD_VALUE` to assess the economic impact of a failed transfer, along with other critical details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/priced-net-transfers-failed-table.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.