Checks
Would a node accept it, and would it relay it?
Screens
What it does
The Checks tab lists what can be checked from the transaction alone. Errors are what every node refuses: no inputs, duplicate inputs, amounts out of range, a malformed coinbase, encodings Bitcoin Core will not read. Warnings are Bitcoin Core 30's relay policy: a transaction a block may contain but default nodes would not pass on.
How it works
Current policy
Versions 1 to 3, version 3 (TRUC) size limits, the 65-byte minimum, standard scripts, dust thresholds including ephemeral dust for pay-to-anchor, and the OP_RETURN rules of Core 30.
Encoding errors
Non-canonical lengths, superfluous witness records, unknown flags and bytes after the end are reported with the rule they break.
Linked to fields
Click a finding to open and mark the field it is about.
Honest limits
Fees, input amounts and signatures need the outputs being spent, which a transaction does not carry, so they are not claimed.
Good to know
- Consensus rules on every network
- Relay policy on Bitcoin and testnet