> 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-table.md). # Priced Net Transfers Table Priced net transfers are a curated table of transfer events for a digital asset. They include all transfers, including the native token and other token types. This table has converted all the values using token metadata and has priced historical asset value to USD. The difference between the net table vs the standard-priced table is that the transfers are broken up into in-flow and out-flow based on sending and receiving parties. It is helpful when evaluating transfers from a party: wallets, exchanges, and smart contracts. | 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 token transfers. analyze token transfers, including both native and non-native assets, where values are converted to USD, among other key attributes. You can: * Identify the block and transaction context with `BLOCK_SLOT`, `TIMESTAMP`, `DATETIME`, `TRANSACTION_INDEX`, and `TRANSACTION_ID`. * Locate the specific instruction using `INSTRUCTION_INDEX` and `INNER_INSTRUCTION_INDEX`. * Determine the transfer direction with `TRANSFER_TYPE` (distinguishing between incoming and outgoing tokens). * Identify the participating parties through `ACCOUNT` and `CP_ACCOUNT`. * Retrieve token details via `TOKEN_ADDRESS`, `NAME`, and `SYMBOL`. * Analyze the transfer amount using VALUE, and understand fee structures with `TOKEN_FEE`, `USD_VALUE`, and `USD_TOKEN_FEE`. * Assess data recency using `DATE_CREATED` and `DATE_UPDATED`. For example, you might query `VALUE`, `TRANSFER_TYPE`, and `USD_VALUE` to distinguish between inflows and outflows and gauge their USD-equivalent impact, along with other key parameters. --- # 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-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.