| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block began. |
| BLOCK_ID | NUMBER | The height of the chain this block corresponds with. |
| TX_HASH | TEXT | Unique identifier (hash) of this transaction. |
| RECEIPT_ID | TEXT | The identifying hash for a receipt. |
| RECEIVER_ID | TEXT | Account reacting to the receipt from predecessorid, can be relay, a contract, or a user of a relay, etc. This field identifies the account that is processing the receipt and executing the associated action. In most cases, this is a smart contract that is being called, but it can also be a user account in relay transactions or the system account for certain operations. This differs from txreceiver and is specific to the receipt being processed. |
| PREDECESSOR_ID | TEXT | Account that called the relevant receipt (often the same as tx_signer, but can be system as well). This field identifies the account that directly invoked the receipt being processed. In simple transactions, this is typically the same as the transaction signer. However, in cross-contract calls or system operations, this may be a different account or the system account. This is crucial for understanding the call chain and access control in NEAR’s execution model. |
| LOG_EVENT | TEXT | Type of NEP245 event (e.g., mttransfer, mtburn, mt_mint) |
| TOKEN_ID | VARIANT | The identifier of the token being transferred or minted. |
| SYMBOL | TEXT | Token symbol (e.g., ‘wNEAR’, ‘SWEAT’). This field contains the abbreviated identifier for the token as commonly used in trading pairs, price feeds, and user interfaces. Token symbols are typically 2-6 characters long and provide a quick way to identify tokens without using their full contract addresses. Examples include ‘NEAR’ for the native token, ‘wNEAR’ for wrapped NEAR, and ‘USDC’ for USD Coin. |
| AMOUNT_ADJ | FLOAT | Decimal adjusted amount of tokens (as float, rounded - use this generally). This field provides the token amount after applying the appropriate decimal precision adjustments based on the token’s decimal places. For example, if transferring 1 NEAR token, the amount_adj would be 1.0 after dividing the raw amount (1e24) by 10^24. This field is the most commonly used representation for token amounts in analytics and reporting as it provides human-readable values. |
| AMOUNT_USD | FLOAT | USD value of the token transfer (null if hourly price not available). This field provides the dollar equivalent value of the token transfer by multiplying the decimal-adjusted token amount by the token’s USD price at the time of the transfer. This field is null when price data is unavailable, which can occur for new tokens, tokens with low liquidity, or during periods when price feeds are unavailable. |
| OWNER_ID | TEXT | Account ID that owns the multi-token (NEP245) assets involved in the intent transaction. For mint events, this is the account receiving the newly created tokens. For burn events, this is the account whose tokens are being destroyed. This field is null for transfer events, which use oldownerid and newownerid instead. The owner_id is critical for tracking token custody and account balances in multi-token intent executions. |
| OLD_OWNER_ID | TEXT | Sender account ID for transfer events |
| NEW_OWNER_ID | TEXT | Receiver account ID for transfer events |
| AMOUNT_RAW | TEXT | Unadjusted amount of tokens as it appears on-chain (not decimal adjusted). This is the raw token amount before any decimal precision adjustments are applied. For example, if transferring 1 NEAR token, the amount_raw would be 1000000000000000000000000 (1e24) since NEAR has 24 decimal places. This field preserves the exact on-chain representation of the token amount for precise calculations and verification. |
| BLOCKCHAIN | TEXT | The name of the blockchain. |
| CONTRACT_ADDRESS | TEXT | The address of the deployed contract for the token, nft, or other smart contract. |
| IS_NATIVE | BOOLEAN | Boolean flag indicating whether the token is the native token of a blockchain (TRUE) or a fungible token contract (FALSE). |
| PRICE | FLOAT | The asset price, in US Dollars. |
| DECIMALS | NUMBER | Number of decimal places for the token. This field specifies the precision of the token, indicating how many decimal places should be used when converting from raw on-chain amounts to human-readable values. For example, NEAR has 24 decimals, so 1 NEAR = 1e24 raw units. Most ERC-20 tokens use 18 decimals, while some tokens may use different precision based on their design requirements. |
| GAS_BURNT | NUMBER | Gas burned for the receipt action. This field represents the amount of computational resources consumed specifically for the receipt being processed. Gas burning is the mechanism by which NEAR charges for computational work, and this field tracks the exact amount burned for this particular receipt action. In raw number format with 16 decimal places, to adjust divide by POW(10,16) or multiply by 1e-16. |
| MEMO | TEXT | Optional log message within the transaction (often null). This field contains additional information or context about the transfer, such as transaction notes, reference numbers, or descriptive text. Memos are commonly used in cross-chain bridges, exchange deposits, or other scenarios where additional context is needed to identify or process the transfer. The memo field is optional and frequently null for standard transfers. |
| REFERRAL | TEXT | ID of the referring protocol, as extracted from the Receipt log. |
| FEES_COLLECTED_RAW | VARIANT | Raw JSON object containing fee information collected from the intent execution, as extracted from the DIP4 event log. This field contains the complete on-chain representation of fees charged by the intent protocol, formatted as a JSON object with token addresses as keys and unadjusted fee amounts as values. For example: {"nep141:wrap.near": "1232145523809524"} indicates fees collected in wrapped NEAR tokens. This field is null when no fees were collected or when fee information is not availab… |
| FEE_TOKEN | TEXT | Token symbol for the fee collected (e.g., ‘NEAR’, ‘USDT’). This field identifies the specific token in which the intent execution fee was charged, extracted and labeled from the feescollectedraw JSON object. Fee tokens are typically stablecoins (like USDT, USDC) or the native protocol token (NEAR), though any supported token can be used for fees. This field is null when no fees were collected or when the fee token cannot be identified in the token metadata. Understanding fee tokens is importa… |
| FEE_AMOUNT_ADJ | FLOAT | Decimal-adjusted fee amount collected from the intent execution. This field provides the fee amount after applying the appropriate decimal precision adjustments based on the fee token’s decimal places. For example, if a fee of 1 USDT was collected, the feeamountadj would be 1.0 after dividing the raw amount by 10^6 (USDT has 6 decimal places). This field is the most commonly used representation for fee amounts in analytics and reporting as it provides human-readable values. This field is null… |
| FEE_AMOUNT_USD | FLOAT | USD value of the fee collected from the intent execution. This field provides the dollar equivalent value of the fee by multiplying the decimal-adjusted fee amount by the fee token’s USD price at the time of the intent execution. This standardized USD representation enables protocol revenue analysis, fee tracking across different tokens, and cost comparisons over time. The field uses ZEROIFNULL to ensure zero values when price data is unavailable rather than null, which simplifies aggregation… |
| DIP4_VERSION | TEXT | Version of the DIP4 standard that emitted the log for this action. |
| LOG_INDEX | NUMBER | Sequential index of the log entry within the receipt |
| LOG_EVENT_INDEX | NUMBER | Position of the event in the log_data array |
| AMOUNT_INDEX | NUMBER | Position of the amount in the flattened amounts array from the NEP245 event |
| RECEIPT_SUCCEEDED | BOOLEAN | Boolean indicating whether the receipt was successfully processed. This field tracks the execution status of the receipt, which is crucial for understanding transaction outcomes. While most transactions succeed, individual receipts within a transaction can fail due to various reasons such as insufficient gas, contract errors, or invalid parameters. This field is essential for filtering successful operations and analyzing failure patterns. |
| TOKEN_IS_VERIFIED | BOOLEAN | Boolean flag indicating whether the token or price record is verified by Flipside’s crosschain curation process. Verified tokens are prioritized for analytics and are considered reliable for most use cases. Unverified tokens may be incomplete, deprecated, or experimental. |
| EZ_TRANSACTIONS_ID | TEXT | A unique identifier for the record. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp at which the record was initially created and inserted into this table. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp at which this record was last modified by an internal process. |
| _INVOCATION_ID | TEXT | A job ID to identify the run that last modified a record. |
