<p>Those are Pay to Pubkey scriptPubKeys. P2PK is in the format <code>&lt;pubkey len&gt; &lt;pubkey&gt; OP_CHECKSIG</code>. The <code>21</code> is the pubkey length and the <code>03</code> is the first byte of the pubkey. The <code>ac</code> is OP_CHECKSIG.</p>

CC BY-SA 3.0
2018-04-23T18:35:38.143Z
Perfect, can't believe I overlooked that.
Josh Hibschman
CC BY-SA 3.0
2018-04-23T18:21:26.087Z
2018-04-23T18:21:26.087Z
Ava Chow
<p>I'm running BitcoinUnlimited's <a href="https://github.com/BitcoinUnlimited/BitcoinUnlimited/tree/giga_perf" rel="nofollow noreferrer">giga_perf branch</a> of bitcoin in regest mode, and I'm noticing a different format than P2PKH in the scriptPubKey when running listunspent over rpc.</p>

<p>Typically I see scriptPubKey's in the P2PKH format:</p>

<pre><code>'76a914' + b58check_to_hex(address) + '88ac'
</code></pre>

<p>But with this implementation I'm seeing:</p>

<pre><code>'2103' + ??? + 'ac'
</code></pre>

<p>Some examples below, what format are these scriptPubKey's in?</p>

<pre><code>{
  "txid": "07ad742b0bab1c5e65fe720459747aa687d293fef0d0f168297bcaafbe73f17b",
  "vout": 0,
  "address": "mrjTCJGC7aYdZsy3gUJMpBesgtH1ymybsN",
  "scriptPubKey": "21031f5ce0854d50e632bd7002ae5aff977396376082e45329fcdf1af52ab68f766bac",
  "amount": 50.00000500,
  "confirmations": 101,
  "spendable": true
}, 
{
  "txid": "d7f623f59d8fa37eea5fafeb3819ecd76750bea9bb48d453e0eb13426c7e707e",
  "vout": 0,
  "address": "n2Faf95smgYu6e9aBVAwwzp6oULnL7SSSs",
  "scriptPubKey": "21039ff795e5433e67b418e100938ac72e2713a1661c15f48a5c198a5086d96285beac",
  "amount": 50.00000000,
  "confirmations": 108,
  "spendable": true
}
</code></pre>

<transactions><public-key><raw-transaction>
What format is this scriptPubKey?
Josh Hibschman
# What format is this scriptPubKey?

(Asked by: username_0 on 2018-04-23)

I'm running BitcoinUnlimited's [giga\_perf branch](https://github.com/BitcoinUnlimited/BitcoinUnlimited/tree/giga_perf) of bitcoin in regest mode, and I'm noticing a different format than P2PKH in the scriptPubKey when running listunspent over rpc.

Typically I see scriptPubKey's in the P2PKH format:

```
'76a914' + b58check_to_hex(address) + '88ac'

```

But with this implementation I'm seeing:

```
'2103' + ??? + 'ac'

```

Some examples below, what format are these scriptPubKey's in?

```
{
  "txid": "07ad742b0bab1c5e65fe720459747aa687d293fef0d0f168297bcaafbe73f17b",
  "vout": 0,
  "address": "mrjTCJGC7aYdZsy3gUJMpBesgtH1ymybsN",
  "scriptPubKey": "21031f5ce0854d50e632bd7002ae5aff977396376082e45329fcdf1af52ab68f766bac",
  "amount": 50.00000500,
  "confirmations": 101,
  "spendable": true
}, 
{
  "txid": "d7f623f59d8fa37eea5fafeb3819ecd76750bea9bb48d453e0eb13426c7e707e",
  "vout": 0,
  "address": "n2Faf95smgYu6e9aBVAwwzp6oULnL7SSSs",
  "scriptPubKey": "21039ff795e5433e67b418e100938ac72e2713a1661c15f48a5c198a5086d96285beac",
  "amount": 50.00000000,
  "confirmations": 108,
  "spendable": true
}

```

**Tags:** transactions, public-key, raw-transaction


---

## 1 answers

### Answer by username_1 on 2018-04-23. Score: 3 | Accepted answer

Those are Pay to Pubkey scriptPubKeys. P2PK is in the format `<pubkey len> <pubkey> OP_CHECKSIG`. The `21` is the pubkey length and the `03` is the first byte of the pubkey. The `ac` is OP\_CHECKSIG.

> **Comments:**
> **username_0**: Perfect, can't believe I overlooked that.  

---

