Invalid block 783426

00000000000000000002ec935e245f8ae70fc68cc828f05bf4cfa002668599e4

Why it is invalid

rule and Core reject
bad-blk-sigops
Core check
ConnectBlock
CI checks
A complete block at mainnet height 481824 or later, authenticated previous transactions for every external input, and calculated BIP16/BIP141 sigop cost above 80000.

Incident note: 783426 and 784121 - F2Pool sigops (2023)

Both blocks exceed the sigop limit: accurate sigop cost 80003 against the 80000 maximum, counted in ConnectBlock. The context-free legacy count is under the limit, which is why replay cannot reproduce bad-blk-sigops. Documented in b10c observation 11. CI reproduces the 80003 cost for each block using previous transactions authenticated against its inputs. Block 783426 has 74520 legacy cost, 160 P2SH cost and 5323 witness cost; block 784121 has 72204, 908 and 6891 respectively. The previous transactions are fetched from public APIs and cached; the block bodies and their witness commitments supply the remaining evidence.

Header

version
0x2b690000 (728301568)
previous block
00000000000000000001244128897a9f32c24ca0e7ee578063f8580deed9ccb7 (canonical, mempool.space)
merkle root
c2ca1250a0ef1a679a0f8a6661304af663452636ab35efc61c75cac55d406548
time
2023-04-01 07:32:51 UTC (1680334371)
bits
0x1706023e difficulty 46,843,400,286,277
nonce
1078359670
header hex
0000692bb7ccd9ee0d58f8638057eee7a04cc2329f7a89284124010000000000000000004865405dc5ca751cc6ef35ab36264563f64a3061668a0f9a671aefa05012cac223de27643e02061776764640

Evidence on file full block

full block
783426-00000000000000000002ec935e245f8ae70fc68cc828f05bf4cfa002668599e4.bin 1,592,012 bytes
record
data/invalid-blocks.jsonl, line 166

Context

pool
F2Pool by tag
coinbase_height
783426
coinbase_scriptsig_hex
0342f40b2cfabe6d6d76eebeccd7ca22e72d1f7c18b9a3ae8c3f93c04072e77b94dfcf0f0dd560be4410000000f09f909f092f4632506f6f6c2f66000000000000000000000000000000000000000000000000000000000000000000000005007c000000
scriptSig as text
·B··,··mmv·····"·-·|·····?··@r·{······`·D·········/F2Pool/f·····································|···

Observations (6)

Where the block was seen or recovered. Observations record acquisition; they do not establish the failure.