> 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-transfers-table.md). # Priced Transfers Table Priced 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. | 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. | | `TRANSACTION_INDEX` | `FIXED` | The position or order of a transaction within a block of the blockchain. | | `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 inner instruction within a transaction. | | `PROGRAM` | `TEXT` | Program or smart contract associated with the instruction. | | `PROGRAM_ID` | `TEXT` | The program ID of the instruction. | | `TYPE` | `TEXT` | The type of the transfer. | | `ACCOUNT_AUTHORITY` | `TEXT` | The authority address that is assigned to the account. | | `SIGNERS` | `VARIANT` | List of signers associated with the instruction. | | `FROM_ACCOUNT_OWNER` | `TEXT` | The owner address of the from account. | | `FROM_ACCOUNT_SOURCE` | `TEXT` | The source address of the from account. | | `FROM_ACCOUNT` | `TEXT` | The projected highest level from account owner based on owner, authority, and source fields in this order. | | `TO_ACCOUNT_OWNER` | `TEXT` | The owner address of the to account. | | `TO_ACCOUNT_DESTINATION` | `TEXT` | The source address of the to account. | | `TO_ACCOUNT` | `TEXT` | The projected highest level to\_account owner based on owner and destination fields in this order. | | `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 the token is being received. | | `TOKEN_FEE` | `REAL` | The fee or royalties associated to the token account. | | `USD_VALUE` | `REAL` | The curated value of the token, priced in USD. | | `USD_TOKEN_FEE` | `REAL` | The token fee priced in USD. | | `SOURCE_VALUE` | `FIXED` | The raw quantity of the token before the decimal conversion. | | `SOURCE_TOKEN_FEE` | `FIXED` | The raw quantity of the token before the decimal conversion. | | `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 transfer events. Analyze token transfers (native or otherwise) with values converted to USD. The table helps you understand which program was involved, when the transfer happened, and the authority address linked to each account, as well as additional essential metrics. You can: * Identify the block and transaction context using `BLOCK_SLOT`, `TIMESTAMP`, `DATETIME`, `BLOCK_HASH`, `TRANSACTION_INDEX`, and `TRANSACTION_ID`. * Locate the specific instruction with `INSTRUCTION_INDEX` and `INNER_INSTRUCTION_INDEX`. * Examine the transfer’s source details through `PROGRAM`, `PROGRAM_ID`, `TYPE`, and `ACCOUNT_AUTHORITY`. * Investigate account participation via `SIGNERS`, `FROM_ACCOUNT_OWNER`, `FROM_ACCOUNT_SOURCE`, `FROM_ACCOUNT`, `TO_ACCOUNT_OWNER`, `TO_ACCOUNT_DESTINATION`, and `TO_ACCOUNT`. * Retrieve token characteristics using `TOKEN_ADDRESS`, `NAME`, and `SYMBOL`. * Analyze the transfer amounts and fee structures with `VALUE`, `TOKEN_FEE`, `USD_VALUE`, `USD_TOKEN_FEE`, `SOURCE_VALUE`, and `SOURCE_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 transfer, plus 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-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.