solana.marinade Table: ez_native_staking_actions Type: Base Table
Description
This table tracks staking actions for accounts that have interacted with Marinade Native Staking at least once. It provides a comprehensive view of native staking activities including deposits, withdrawals, and balance changes, with USD pricing information and validator details, enabling analysis of Marinade’s native staking proxy service.Key Use Cases
- Analyze native staking patterns through Marinade’s proxy service
- Track stake account lifecycle and balance changes
- Monitor validator delegation patterns and performance
- Study user behavior in native staking through Marinade
- Support native staking proxy service performance analysis
Important Relationships
- Links to
silver.staking_lp_actions_labeled_2for detailed staking action data - Connects to
gov.fact_stake_accountsfor stake account information - References
price.ez_prices_hourlyfor USD price conversion - Provides native staking context for Marinade Finance ecosystem analytics
Commonly-used Fields
block_timestamp: Essential for time-series analysis and trend detectionevent_type: Critical for categorizing different staking activitiesprovider_address: Key for user analysis and behavior trackingstake_account: Important for stake account lifecycle trackingpre_tx_staked_balanceandpost_tx_staked_balance: Critical for balance change analysisvalidator_nameandvalidator_rank: Key for validator performance analysis
Columns
| Column Name | Data Type | Description |
|---|---|---|
| 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. |
- 123456789
- Supports block-level analytics, such as block production rate and transaction throughput.
- Useful for tracing transaction inclusion and block explorer integrations.
- All transactions with the same ‘block_id’ share the same ‘block_timestamp’. | | 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 block explorers or Solana APIs.
5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw
- Enables precise tracking, auditing, and attribution of on-chain activity
- Used for linking transactions to events, logs, and protocol actions
- Critical for compliance, monitoring, and analytics workflows | | INDEX | NUMBER | The position of the transfer event within the list of events for a given Solana transaction. Used to order and reference transfers within a transaction. Indexing starts at 0 for the first event.
- 0 (first transfer in the transaction)
- 2 (third transfer in the transaction)
- Enables reconstruction of transfer order and analysis of intra-transaction asset movement.
- Used to join, filter, or segment data for protocol analytics, error tracing, and event sequencing. | | 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.
- 0
- 2
- 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. | | SUCCEEDED | BOOLEAN | Boolean flag indicating whether the transaction was successfully executed and confirmed on the Solana blockchain. A value of TRUE means the transaction was processed without errors; FALSE indicates failure due to program errors, insufficient funds, or other issues.
- true
- false
- Used to filter for successful transactions in analytics and reporting.
- Important for error analysis, user experience, and program debugging. | | EVENT_TYPE | TEXT | A string categorizing the type of event or instruction, such as ‘transfer’, ‘mint’, ‘burn’, or protocol-specific actions.
- ‘transfer’
- ‘mint’
- ‘burn’
- Enables segmentation and filtering of on-chain activity for analytics and dashboards.
- Used to group and analyze protocol-specific actions and user behaviors.
- May be derived from decoded instruction data or protocol-specific logic. | | PROVIDER_ADDRESS | TEXT | The provider address is the same as the withdraw authority which is defined as…The account responsible for signing any stake withdrawal transactions. This field identifies who has authority to withdraw staked SOL from the account.
- “4Nd1mY…”
- “TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA”
- Used as a join key for program activity, deployments, events, and interface changes.
- Supports segmentation of activity by protocol, DEX, NFT marketplace, or other on-chain application. | | PLATFORM | TEXT | The platform of the staking account, either native or marinade native proxy. This field identifies whether the staking action is using direct native staking or Marinade’s native staking proxy service, enabling platform-specific analysis.