Script Editor
Scripts one operation per line, explained as you go.
Screens
What it does
Each script is shown one operation per line, in the format TransactionBuilder used: opcodes by name, and every push followed by its data. The column beside it says what each item is, a DER signature with its sighash type, a compressed public key, a 20-byte hash, and the hex view marks the bytes of the line the caret is on.
How it works
The original format
OP_DUP, DATA_20 followed by [DATA] ***…***, OP_PUSHDATA1 with its size line: scripts read and write the way they did in TransactionBuilder.
Type data, not lengths
A [DATA] line, or plain hex, with no push before it gets the shortest push automatically.
Paste ASM
mempool.space style ASM on one line, OP_PUSHBYTES_20 followed by the hex, is understood as well.
Every item described
Signatures with their sighash type, public keys, hashes, witness programs, numbers and text, so a script reads like a sentence.
Mistakes stay visible
An unknown word is an error on its line instead of a silent zero byte; a push whose data has a different length is a warning, and is written as typed.
Spends recognised
Each input says what it most likely spends, P2PKH, P2SH multisig, P2WPKH, P2TR, and the address it spends from when the input reveals it.
Good to know
- All opcodes, OP_CHECKSIGADD included
- Raw bytes as 0xNN, comments with #
- Redeem and witness scripts decoded
- Bitcoin Core style ASM shown too