| BLOCK_ID | NUMBER | The height of the chain this block corresponds with. |
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block began. |
| TX_HASH | TEXT | Unique identifier (hash) of this transaction. |
| 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 |
| TOKEN_ADDRESS | TEXT | The contract address corresponding to the token, view details of the contract by following this address on the chain explorer. |
| TOKEN_ADDRESS_RAW | VARIANT | The raw token identifier as it appears on-chain, including the full token ID with blockchain prefix and contract address. For NEAR tokens, this includes the full token ID format (e.g., ‘nep141:token.near.omft.near’). This field preserves the original token representation before any parsing or standardization is applied. |
| AMOUNT_UNADJ | 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. |
| AMOUNT_ADJ | TEXT | 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. |
| DESTINATION_ADDRESS | TEXT | The address tokens are being sent to, in a transfer or bridge transaction. |
| SOURCE_ADDRESS | TEXT | The originating address from which tokens are being sent, in a transfer or bridge transaction. This addressed is ascertained as best as possible, but may be null depending on the available information. Example 1 - tx CzPRdoiU74bo9yqqt9fCP5Xdab2mPVqxr9gU5xeaQA4a stores just “signerpublickey 0x0x1589…f694” on chain. Example 2 - tx FA7tQeGQnhminbas28YgaizwmT4vnEUiCr3vdXmN3Xjn does not log any signing address at all. |
| PLATFORM | TEXT | The protocol utilized for the operation, likely a swap or bridge. |
| BRIDGE_ADDRESS | TEXT | The address of the deployed contract for the token, nft, or other smart contract. |
| DESTINATION_CHAIN | TEXT | The recipient blockchain in a bridge transaction. |
| SOURCE_CHAIN | TEXT | The originating blockchain in a bridge transaction. |
| METHOD_NAME | TEXT | Name of the method(s) approved for use. NULL if permission is FullAccess. |
| DIRECTION | TEXT | Direction of funds through a bridge. Inbound = tokens bridged to Near ecosystem. Note - for the Rainbow bridge, inbound means Near or Aurora as tokens pass through Near to get to Aurora. |
| 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. |
| FACT_TRANSACTIONS_ID | TEXT | A unique identifier for the record. |
| FACT_BRIDGES_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. |
