BTC: Blocks with Conflicting Mining Labels

Bitcoin Blocks with Conflicting Mining Labels was 0 blocks on 7 Nov 2026 (latest daily value).

Observed canonical blocks whose coinbase facts match conflicting mining labels.

Why use it. See where the matching rule cannot choose a single label. How to read it. The pinned label list is applied retrospectively. Tags can be spoofed, and different labels can belong to the same operator. Read label coverage alongside these observations. An ambiguous block is not divided among candidates or arbitrarily assigned to one. This category does not establish collaborative mining or an operator count. A missing scalar bucket is undefined, not zero. Missing coinbase facts stop the calculation frontier; they are not classified as Unknown blocks. Read actual source coverage and clocks. Open periods remain partial; MTP closure and six later canonical blocks govern finality. The calculation describes unsmoothed observations; chart smoothing is a separate transform.

Calculation. Count each block with more than one candidate once in Ambiguous. Recognized, Unknown and Ambiguous block counts partition the observed canonical population. Match literal UTF-8 coinbase-tag bytes with ASCII-only case folding, together with the exact canonical address of coinbase output 0. One candidate gives a named label, none gives Unknown and conflicting candidates give Ambiguous. Assign complete canonical blocks to UTC hours or days using their header timestamps, retaining timestamp regressions. Use locally validated canonical coinbase facts and the pinned MIT-licensed mining-pool definitions; credits and the dataset revision remain in method details.