3 datasets
Timestamps at which blocks arrived at various Bitcoin nodes, one CSV file per node with height, hash and millisecond arrival time. Contributors extract the timestamps from their Bitcoin Core debug logs with the included script, and CI checks them against the block header time. Useful for measuring block propagation delay; coverage differs by node and period.
Bitcoin blocks with valid proof of work that fail a named consensus rule, one JSON record per header with the failure reason, evidence and observations. Records come from the P2P network, merge-mined chains and archived block explorers, and CI verifies each record's proof of work and evidence. Useful for studying consensus failures and historical incidents; blocks only reported as invalid are kept in a separate file.
Stale Bitcoin blocks and headers observed on the network, one CSV row per block with height, hash and raw header, plus full blocks where available. Node operators contribute their chain tips from Bitcoin Core's getchaintips RPC, supplemented by fork monitors and block explorer archives. Useful for stale- block rates and propagation studies; listed blocks are not verified to be fully consensus-valid.