Invalid block 175849

00000000000009ae68befcafac4f8178781026e5a7885af40c38fd8fa79597d7

Why it is invalid

rule
prev_block_invalid
Core reject
bad-prevblk
Core check
AcceptBlockHeader
CI checks
parent_kind=invalid: prev_hash is a record in this dataset at height minus one. The header alone is the evidence.

Incident note: 173928, 173957, 173998 and 174605 - P2SH redeem-script failure (2012)

Each body includes the same 123-byte transaction, 4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2, which spends a pay-to-script-hash output funded at canonical 170054, b0539a45de13b3e0403909b8bd1a555b8cbe45fd4e3f3fda76f3a5f52835c29d:1, worth 400000 satoshis. Its scriptSig pushes only the redeem script, a 1-of-1 OP_CHECKMULTISIG. The pre-BIP16 template check hashes that push and compares it, and passes; executing the redeem script finds no signature on the stack and fails. Nodes applying the 1 April 2012 rules rejected these blocks while older nodes accepted them, which is how the same transaction was included by many miners for months. Core today reports block-script-verify-flag-failed (Operation not valid with the current stack size).

Header

version
0x00000001 (1)
previous block
00000000000001fc57f777551905e43c30f943ad9feffcfa6aa7693ccfad03d8 (invalid, in this dataset)
merkle root
effb5b434def1de29ff5c4dbbab9a41ca2545b34c57beade3a4507716c9fa20e
time
2012-04-16 07:13:11 UTC (1334560391)
bits
0x1a0aa1e3 difficulty 1,577,913
nonce
3209254483
header hex
01000000d803adcf3c69a76afafcef9fad43f9303ce405195577f757fc010000000000000ea29f6c7107453adeea7bc5345b54a21ca4b9badbc4f59fe21def4d435bfbef87c68b4fe3a10a1a535649bf

Evidence on file full block

full block
175849-00000000000009ae68befcafac4f8178781026e5a7885af40c38fd8fa79597d7.bin 33,997 bytes
record
data/invalid-blocks.jsonl, line 83

Context

pool
OzCoin by tag
coinbase_scriptsig_hex
1265636f406f7a636f2e696e202f503253482f0487c68b4f021b052cfabe6d6dcdba49266e15033648646283ba6b1e7f9ff29c559dc6f9db3a82ed57f3d5edc30100000000000000
scriptSig as text
·eco@ozco.in /P2SH/····O···,··mm··I&n··6Hdb··k·····U····:··W············

Observations (5)

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