Paste a block to see exactly what it does before you sign it. An unsigned proposal arrives as JSON; a signed block as hex or JSON.
Sign this block
Your secret is typed into this page. Only do this on a machine you trust, with a
file you obtained yourself. Nothing is stored, sent, or written to disk — but a page from
an untrusted source could do all three, and you cannot tell by looking. Read the block above
before signing: a signature commits you to it irrevocably.
What this does and does not tell you
The hash is recomputed from what you pasted. If it matches what you were asked to sign, this is the block — that is the check that matters. A hash inside pasted JSON is ignored, never trusted.
Every field the library reads out of the block is shown. A field this tool does not recognise is shown raw and flagged in red: do not sign it.
Amounts are shown in raw base units. Converting to human units needs the token's decimals, which is a network lookup and is deliberately not done here.
Every address shows its key type. MULTISIG (0x07) and other identifier types cannot sign or spend — funds sent to them are stranded.
For multisig blocks, the signer container lists the signers this block carries. The on-chain quorum is not in the bytes; verify separately that this set satisfies it.
This shows what the block does, not what it means. It has no balances, no account names, no notion of whether the result is sensible.
Verify it is offline: load the file, disconnect the network, decode. Nothing is fetched and nothing is sent.