Script Lab
Interactive Bitcoin Script execution engine — write, step, and debug raw opcodes.
Execution Readiness
Step/Run now executes the real interpreter trace endpoint using tx context, flags, and satoshi amounts.
Real consensus API: ... total opcodes (0 enabled / 0 disabled / 0 reserved) via bitcore interpreter.
Arithmetic + comparison workflow.
Objective: Prove 1 + 1 == 2 and finish true.
Validation Engine
Run the script to evaluate objective and consensus result.
Consensus: Pending
Scenario objective: Pending
Hint: Consensus trace returns minimally-encoded script numbers as hex stack items.
Main Stack (0)
Alt Stack (0)
Execution Trace
Pointer: 0
No executed opcodes yet.
Opcode Stream
Consensus Opcode Catalog
Real catalog from bitcore interpreter: 0 total, 0 enabled, 0 disabled, 0 reserved.
Catalog unavailable.
Consensus Verify (Real Engine)
Uses bitcore-lib Interpreter with policy/consensus flags, tx context, witness and satoshi input.
Real Fixture Library
Deterministic transaction contexts for legacy, segwit, taproot, timelock constraints, and sighash failures.
Verification Flags
Consensus Result
No consensus result yet.
Trace Result (Real Interpreter)
No real trace result yet.
Bitcoin Script Lab and Debugger
Step through Bitcoin Script with a visual stack machine, opcode highlighting, and consensus trace presets for common locking patterns.
Load scenarios for P2PKH, multisig, Taproot key-path spends, and custom scripts to see exactly where validation succeeds or fails.
Frequently asked questions
Does the Script Lab execute real mainnet transactions?
No. It interprets script snippets locally for education. Use the transaction decoder to inspect confirmed on-chain scripts.
Can I paste my own script hex?
Yes. Enter hex or assembly-style script fragments and advance opcode-by-opcode through the stack trace.