ethereum.beacon_chain Table: fact_withdrawals Type: View
What
This model details the withdrawals that have been made from the beacon chain of Ethereum.Columns
| Column Name | Data Type | Description |
|---|---|---|
| SLOT_NUMBER | NUMBER | The Beacon Chain slot this block represents. |
| SLOT_TIMESTAMP | TIMESTAMP_NTZ | Timestamp of Beacon Chain slot. |
| EPOCH_NUMBER | NUMBER | A period of 32 slots, each slot being 12 seconds, totaling 6.4 minutes. |
| WITHDRAWAL_AMOUNT | FLOAT | The amount of ETH that was withdrawn from the beacon chain. |
| WITHDRAWAL_ADDRESS | TEXT | The address that the ETH was withdrawn to. |
| WITHDRAWAL_INDEX | NUMBER | The index of the withdrawal event. |
| VALIDATOR_INDEX | NUMBER | The index of the validator that made the withdrawal. |
| FACT_WITHDRAWALS_ID | TEXT | Primary key - unique identifier for each row ensuring data integrity. Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(blocknumber, txhash, trace_index) Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records Important: Implementation varies by table - check table-specific documentation. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases: Data freshness monitoring Incremental processing markers Debugging data pipeline issues SLA tracking Query Example: |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Triggers for Updates: Data corrections Enrichment additions Reprocessing for accuracy Schema migrations Monitoring Usage: |