| BLOCK_ID | NUMBER | A unique identifier for the block in which this transaction was included on the Solana blockchain. Typically a sequential integer or hash, depending on the data source. Used to group transactions by block and analyze block-level activity. Example: 123456789 Business Context: Supports block-level analytics, such as block production rate and transaction throughput. Useful for tracing transaction inclusion and block explorer integrations. Relationships: All transactions with the same ‘blockid’ s… |
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The timestamp (UTC) at which the block was produced on the Solana blockchain. This field is recorded as a TIMESTAMP data type and represents the precise moment the block was finalized and added to the chain. It is essential for time-series analysis, block production monitoring, and aligning transaction and event data to specific points in time. Used extensively for analytics involving block intervals, network activity trends, and historical lookups. Format: YYYY-MM-DD HH:MI:SS (UTC). |
| TX_ID | TEXT | The unique transaction signature (hash) for each transaction on the Solana blockchain. This field is a base58-encoded string, typically 88 characters in length, and serves as the primary identifier for transactions across all Solana data models. Used to join transaction data with related tables (blocks, events, transfers, logs, decoded instructions) and to trace the full lifecycle and effects of a transaction. Essential for transaction-level analytics, debugging, and cross-referencing with bl… |
| INDEX | NUMBER | The position of the event (instruction) within the list of instructions for a given Solana transaction. Used to order and reference events within a transaction. Indexing starts at 0 for the first event. Example: 0 3 Business Context: Enables precise identification and ordering of events within a transaction, which is critical for reconstructing transaction flows and analyzing protocol behavior. Used to join or filter event-level data, especially when multiple events occur in a single transact… |
| INNER_INDEX | NUMBER | The position of the inner instruction or event within the list of inner instructions for a given Solana transaction. Used to order and reference nested (CPI) instructions. Indexing starts at 0 for the first inner instruction. Example: 0 2 Business Context: Enables precise identification and ordering of nested program calls (Cross-Program Invocations) within a transaction. Critical for analyzing composability, protocol integrations, and the full execution path of complex transactions. |
| ACTION_TYPE | TEXT | The type of event action being performed |
| PROVIDER_ADDRESS | TEXT | The address of the liquidity provider who is performing the deposit or withdrawal action. This field identifies the user providing or removing liquidity from the pool. Data type: STRING (base58 Solana address) Business context: Used to track liquidity providers, analyze provider behavior, and identify active liquidity participants. Analytics use cases: Liquidity provider analysis, provider behavior studies, and liquidity provision tracking. Example: ‘4Nd1mYw4r…’ |
| DEPOSIT_AMOUNT | FLOAT | The amount of SOL deposited into the liquid staking protocol. This field tracks the quantity of SOL being staked through Marinade Finance, enabling deposit analysis and staking volume measurement. Data type: DECIMAL (SOL amount) Business context: Used to track staking deposits, analyze staking volume patterns, and measure protocol usage. Analytics use cases: Deposit tracking, volume pattern analysis, and usage measurement. Example: 10.0, 100.0, 1000.0 |
| DEPOSIT_AMOUNT_USD | FLOAT | The amount of SOL deposited in USD value. This field provides the USD equivalent of the deposited SOL, enabling financial analysis and value-based metrics. Data type: DECIMAL (USD amount) Business context: Used to track deposit values, analyze financial metrics, and measure protocol TVL impact. Analytics use cases: Value tracking, financial analysis, and TVL impact measurement. Example: 100.0, 1000.0, 10000.0 |
| MSOL_MINTED | FLOAT | The amount of MSOL (Marinade Staked SOL) minted. This field tracks the quantity of MSOL tokens created when SOL is deposited into the liquid staking protocol, enabling MSOL supply analysis. Data type: DECIMAL (MSOL amount) Business context: Used to track MSOL minting, analyze supply growth, and measure staking efficiency. Analytics use cases: Minting tracking, supply analysis, and efficiency measurement. Example: 9.95, 99.5, 995.0 |
| MSOL_BURNED | FLOAT | The amount of MSOL (Marinade Staked SOL) burned. This field tracks the quantity of MSOL tokens destroyed when users unstake or claim rewards, enabling MSOL supply analysis. Data type: DECIMAL (MSOL amount) Business context: Used to track MSOL burning, analyze supply reduction, and measure unstaking activity. Analytics use cases: Burning tracking, supply analysis, and unstaking activity measurement. Example: 9.95, 99.5, 995.0 |
| CLAIM_AMOUNT | FLOAT | The amount of SOL claimed from the liquid staking protocol. This field tracks the quantity of SOL withdrawn when users claim their staking rewards or unstake, enabling claim analysis and reward tracking. Data type: DECIMAL (SOL amount) Business context: Used to track claim amounts, analyze reward distributions, and measure unstaking activity. Analytics use cases: Claim tracking, reward analysis, and unstaking measurement. Example: 10.5, 105.0, 1050.0 |
| CLAIM_AMOUNT_USD | FLOAT | The amount of SOL claimed in USD value. This field provides the USD equivalent of the claimed SOL, enabling financial analysis and value-based metrics. Data type: DECIMAL (USD amount) Business context: Used to track claim values, analyze financial metrics, and measure reward distributions. Analytics use cases: Value tracking, financial analysis, and reward measurement. Example: 105.0, 1050.0, 10500.0 |
| PROGRAM_ID | TEXT | The unique public key (base58-encoded address) of a Solana program. This field identifies the on-chain program (smart contract) responsible for processing instructions, emitting events, or managing accounts. Used throughout Solana analytics models—including events, transactions, IDLs, and program activity tables—to join, filter, and analyze program-level data. Example: “4Nd1mY…” “TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA” Business Context: Used as a join key for program activity, deployme… |
| MARINADE_EZ_LIQUID_STAKING_ACTIONS_ID | TEXT | A unique, stable identifier for each record in this table. The primary key (PK) ensures that every row is uniquely identifiable and supports efficient joins, lookups, and data integrity across models. The PK may be a natural key (such as a blockchain transaction hash) or a surrogate key generated from one or more fields, depending on the table’s structure and requirements. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was first inserted into the analytics database. Used for data freshness tracking and incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was last updated in the analytics database. Used for tracking updates and supporting incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. |
| SIGNER | TEXT | The Solana address (public key, base58-encoded) that signed the transaction. Signers are responsible for authorizing transactions and may represent users, programs, or system accounts. In most cases, the first signer is the fee payer. This field enables analysis of user activity, protocol adoption, and transaction attribution. Example: ‘7Ggk7Q2…’. |