| Dataset Name | Schema | Description | Prefix | EthPandaOps Clickhouse | Public Parquet Files |
|---|---|---|---|---|---|
| Beacon API Event Stream | Schema | Events derived from the Beacon API event stream. This data is usually useful for 'timing' events, such as when a block was seen by a sentry. Because of this it usually has the same data but from many different instances. These tables are usually fairly slim and contain only a few columns. These tables can be joined with the canonical tables to get a more complete view of the data. For example, you can join the beacon_api_eth_v1_events_block table on block_root or slot with the canonical_beacon_block table to get the block data for each block. | beacon_api_ | ✅ | ✅ |
| Execution Layer P2P | Schema | Events from the execution layer p2p network. This data is usually useful for 'timing' events, such as when a transaction was seen in the mempool by an instance. Because of this it usually has the same data but from many different instances. | mempool_ | ✅ | ✅ |
| Canonical Beacon | Schema | Events derived from the finalized beacon chain. This data is only derived by a single instance, are deduped, and are more complete and reliable than the beacon_api_ tables. These tables can be reliably JOINed on to hydrate other tables with information | canonical_beacon_ | ✅ | ✅ |
| Canonical Execution | Schema | Data extracted from the execution layer. This data is only derived by a single instance, are deduped, and are more complete and reliable than the execution_layer_p2p tables. These tables can be reliably JOINed on to hydrate other tables with information | canonical_execution_ | ✅ | ✅ |
| Consensus Layer P2P | Schema | Events from the consensus layer p2p network. This data is usually useful for 'timing' events, such as when a block was seen by a sentry. Because of this it usually has the same data but from many different instances. | libp2p_ | ✅ | ✅ |
| Beacon Synthetic | Schema | Events synthesized from the internals of instrumented beacon nodes, such as fork choice payload status changes and builder payment settlement. Each instance records its own view, so the same event usually appears once per instance. | beacon_synthetic_ | ✅ | ✅ |
| MEV Relay | Schema | Events derived from MEV relays. Data is scraped from multiple MEV Relays by multiple instances. | mev_relay_ | ✅ | ✅ |
| CBT (ClickHouse Build Tools) | Schema | Pre-aggregated analytical tables for common blockchain queries. These tables are transformation tables similar to DBT, powered by xatu-cbt using ClickHouse Build Tools (CBT). | ✅ | ❌ |