ethereum.beacon_chain Table: fact_blob_sidecars Type: View
What
This table contains details about blob sidecars directly from the /eth/v1/beacon/blob_sidecars/ rpc endpoint.Columns
| Column Name | Data Type | Description |
|---|---|---|
| BLOB | TEXT | The blob of data associated with the sidecar. |
| BLOB_INDEX | NUMBER | The index of the sidecar. |
| KZG_COMMITMENT | TEXT | The KZG commitment for the data. |
| KZG_COMMITMENT_INCLUSION_PROOF | ARRAY | An array of KZG commitment inclusion proof hashes. |
| KZG_PROOF | TEXT | The KZG proof for the data. |
| BODY_ROOT | TEXT | The body root hash. |
| PARENT_ROOT | TEXT | The parent root hash. |
| PROPOSER_INDEX | NUMBER | The index of the proposer for the slot / block. |
| SLOT_NUMBER | NUMBER | The slot number where the blob was included. |
| STATE_ROOT | TEXT | The state root hash. |
| SIGNATURE | TEXT | The signature hash of the message object. |
| 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: |
| FACT_BLOB_SIDECAR_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. |