Contribute to the Xatu dataset by running xatu sentry against your beacon node, with privacy levels you control.
How to work with Xatu data: public parquet files, your own ClickHouse, or the EthPandaOps ClickHouse cluster.
Open data on the Ethereum network: beacon chain events, mempool activity, canonical chain data, MEV, and p2p networking — from production networks and upgrade devnets.
Which networks Xatu collects from: production networks with coverage, and devnets testing upcoming upgrades.
Search every Xatu table across all datasets and networks — by name, column, or description.
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.
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.
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.
Pre-aggregated analytical tables for common blockchain queries powered by xatu-cbt and Clickhouse Build Tools. These tables are organized by network-specific databases and include dimension, fact, and intermediate tables for analyzing blockchain data.
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.
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.
Events derived from MEV relays. Data is scraped from multiple MEV Relays by multiple instances.
Devnet-only Xatu tables being tested for the Fusaka network upgrade.
Devnet-only Xatu tables being tested for the Glamsterdam network upgrade.
Experimental Xatu data from devnets testing upcoming network upgrades. Devnets run xatu from a fork branch and carry tables that don't exist on production networks yet, each in its own network-specific database.