<p>Surprisingly, there's a number of UTXO entries for the obscure hybrid key format. The transaction <a href="https://blockstream.info/tx/657aecafe66d729d2e2f6f325fcc4acb8501d8f02512d1f5042a36dd1bbd21d1?expand" rel="nofollow noreferrer">657aecafe66d729d2e2f6f325fcc4acb8501d8f02512d1f5042a36dd1bbd21d1</a> makes a number of interesting P2PK outputs, two each of which are <code>0x06</code> and <code>0x07</code> respectively.</p>
<pre><code>OP_PUSHBYTES_65 06da9be28d6e6266ddc0bc71b09032f3a810ffc917b5876e23a03c118f24f6a84dae4a9a5244fbf47860bc0760102d6bde6257bfcb7155d3dd66b97181119f98c5 OP_CHECKSIG

OP_PUSHBYTES_65 07d19ef6ba5b92b87078dba3a00df392efc16917defb2be08f22e41ce2873335705bff95fed463550f291d3b1fd559af11e432256a47e738572be3b74fc6f73ed0 OP_CHECKSIG
</code></pre>
<p>None are spent, but there's no technical reason for this, the outputs are valid.</p>

CC BY-SA 4.0
2021-01-31T16:25:46.303Z
Looks like a good way to waste btc on fees by adding more bytes to your transaction to me ;-)
Robherc KV5ROB
CC BY-SA 4.0
2021-01-31T15:24:53.800Z
2021-01-31T15:24:53.800Z
Claris
<p>If so, could you please give the TXID of a transaction that spends from a <a href="https://bitcoin.stackexchange.com/q/57855/38618">hybrid public key</a>?</p>

<public-key>
Has a spend from a hybrid public key ever made it to the blockchain?
MCCCS
# Has a spend from a hybrid public key ever made it to the blockchain?

(Asked by: username_0 on 2021-01-31)

If so, could you please give the TXID of a transaction that spends from a [hybrid public key](https://bitcoin.stackexchange.com/q/57855/38618)?

**Tags:** public-key


---

## 1 answers

### Answer by username_1 on 2021-01-31. Score: 3 | Accepted answer

Surprisingly, there's a number of UTXO entries for the obscure hybrid key format. The transaction [657aecafe66d729d2e2f6f325fcc4acb8501d8f02512d1f5042a36dd1bbd21d1](https://blockstream.info/tx/657aecafe66d729d2e2f6f325fcc4acb8501d8f02512d1f5042a36dd1bbd21d1?expand) makes a number of interesting P2PK outputs, two each of which are `0x06` and `0x07` respectively.

```
OP_PUSHBYTES_65 06da9be28d6e6266ddc0bc71b09032f3a810ffc917b5876e23a03c118f24f6a84dae4a9a5244fbf47860bc0760102d6bde6257bfcb7155d3dd66b97181119f98c5 OP_CHECKSIG

OP_PUSHBYTES_65 07d19ef6ba5b92b87078dba3a00df392efc16917defb2be08f22e41ce2873335705bff95fed463550f291d3b1fd559af11e432256a47e738572be3b74fc6f73ed0 OP_CHECKSIG

```

None are spent, but there's no technical reason for this, the outputs are valid.

> **Comments:**
> **username_2**: Looks like a good way to waste btc on fees by adding more bytes to your transaction to me ;-)  

---

