Analysis

Crafting

In BScriptView 0.1.0 · free

Build the transaction a node should refuse.

Screens

01 / 01

An overridden script length shown in salmon, with the parser's warning — Unlock a length or a count to write any value: the field turns salmon and Checks says how a node would read it.

What it does

Counts and script lengths are normally derived from what they describe. Tick the box beside one and it can be set to anything, as in the original TransactionBuilder: the field turns salmon, the value is written as typed, and Checks tells you where a parser reading those bytes would stop.

How it works

Overrides

Number of inputs and outputs, and each script's length, can be overridden independently.

Raw bytes

Write any byte in a script with 0xNN, including undefined opcodes and truncated pushes.

Read back

Every encoded transaction is parsed again, so a mismatch shows as the error a node would hit.

Malformed input welcome

Half-typed or broken hex is decoded as far as it goes; the unread bytes are struck through.

Good to know

Salmon marks an overridden value
Nothing is ever broadcast