I have a question regarding this transaction where the outputs are showing as non-standard but appear to be multi-sigs. This is the first output:

Transaction ID: 54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713


Is there an issue with the public key hashes or the script? I am new to this so sure I am missing something simple.

Thank you


1 Answer 1


OP_CHECKMULTISIG is typically preceded by:

  • The number of keys (n)
  • n public keys (not public key hashes!)
  • The number of signatures required (k)

That is not the case here, because the 3 byte arrays that are pushed in between the OP_3 and the OP_1 are not public keys. Public keys are either:

  • 33 bytes, starting with 0x02 or 0x03 (so-called compressed public keys)
  • 65 bytes, starting with 0x04

The byte arrays pushed here are 65 bytes, but do not start with 0x04.

  • 1
    This is data store tx bitcoin.stackexchange.com/questions/35959
    – amaclin
    Jan 30, 2022 at 16:30
  • Thank you Pieter and amaclin. I should have googled the transaction ID. I assume that it is not possible to spend these outputs as there is not corresponding private keys to enable the OP_CHECKMULTISIG to succeed. And thank you for correcting my mistake in the original question.
    – visualAd
    Jan 30, 2022 at 17:55
  • 1
    @visualAd Indeed, it is unspendable. Jan 30, 2022 at 18:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.