Skip to main content
Schema: ethereum.beacon_chain Table: fact_blob_sidecars Type: View This table contains details about blob sidecars directly from the /eth/v1/beacon/blob_sidecars/ rpc endpoint.

​
Columns

Column NameData TypeDescription
BLOBTEXTThe blob of data associated with the sidecar.
BLOB_INDEXNUMBERThe index of the sidecar.
KZG_COMMITMENTTEXTThe KZG commitment for the data.
KZG_COMMITMENT_INCLUSION_PROOFARRAYAn array of KZG commitment inclusion proof hashes.
KZG_PROOFTEXTThe KZG proof for the data.
BODY_ROOTTEXTThe body root hash.
PARENT_ROOTTEXTThe parent root hash.
PROPOSER_INDEXNUMBERThe index of the proposer for the slot / block.
SLOT_NUMBERNUMBERThe slot number where the blob was included.
STATE_ROOTTEXTThe state root hash.
SIGNATURETEXTThe signature hash of the message object.
INSERTED_TIMESTAMPTIMESTAMP_NTZUTC 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: 
-- Check data latency
SELECT
    DATE_TRUNC('hour', block_timestamp) as block_hour,
    DATE_TRUNC('hour', inserted_timestamp) as insert_hour,
    AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes
FROM <blockchain_name>.core.fact_transactions
WHERE block_timestamp >= CURRENT_DATE - 1
GROUP BY 1, 2;
``` |
| 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**:
```sql
-- Recently modified records
SELECT *
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
AND modified_timestamp >= CURRENT_DATE - 1;

-- Data quality tracking
SELECT
    DATE(modified_timestamp) as mod_date,
    COUNT(*) as records_updated,
    COUNT(DISTINCT block_number) as blocks_affected
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
GROUP BY 1
ORDER BY 1 DESC;
``` |
| 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(block_number, tx_hash, 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. |