UNKNOWN
UNKNOWN ⓘ Unknown opcode 0x65 5 confirmationsEnvelope wrapper parsed correctly but the opcode byte isn't defined in the v1 spec. Per SPEC §5 the indexer treats this as a no-op — it could be a future-spec opcode, a wallet bug, or someone testing the envelope path.
Transaction
- txid · reveal
- 49e187efb8b1bd45c6debf0d2a7d0c5b02296b8f2683189797cd9ea286567164
- status
- 5 confirmations
- block
- 966510 · tx_index 1
- block_hash
- 000000000000000000005f73bcaf819e50ceee688d02eb99a442d0159c3404ad
- block_time
- 2026-09-11T13:40:05.000Z · 1h ago
- fee
- 31546 sats
- vin / vout
- 1 / 1
Envelope
- opcode
- UNKNOWN — see SPEC.md §5
Signatures & proofs
Raw
- witness (208 B)
- 203e6eab80a246893f877785fc9d49edf878c88a77397787922274677164c75d45ac006305544143495401014ca165f0bbe868af10c6c67652a99709bf32048d1aa7194efe3e9a1ef1bde43f94762b23a70ac7d0b3606e66763fde1277c15ffcebc34b5f1dd102fdcfa650ce2d7318cfae183006b2648892ecb243fd1aee1604d5930a3f553992175759bc3896ebce7cbdebdb4b58d84ddfbcdfebb82cda4adec64a66f1a5d988a50c4cafc626efbc855dcb0890677d14e06a0c2de83e4c895184d198f22cb11e32b054820efc7c7c68
- payload (161 B)
- 65f0bbe868af10c6c67652a99709bf32048d1aa7194efe3e9a1ef1bde43f94762b23a70ac7d0b3606e66763fde1277c15ffcebc34b5f1dd102fdcfa650ce2d7318cfae183006b2648892ecb243fd1aee1604d5930a3f553992175759bc3896ebce7cbdebdb4b58d84ddfbcdfebb82cda4adec64a66f1a5d988a50c4cafc626efbc855dcb0890677d14e06a0c2de83e4c895184d198f22cb11e32b054820efc7c7c