<p>It is a public key. I think you're parsing this transaction incorrectly - what you should get is that there are two elements. The first is a signature, and 73 bytes long, starting with <code>3046022100ee238c...</code> The second element is a public key, and 33 bytes long, and starts with <code>03b2abe09a1c4e67...</code></p>

<hr>

<p>Here's the transaction you linked, broken up into sig and pubkey.</p>

<p>version</p>

<pre><code>01000000
</code></pre>

<p>vin count</p>

<pre><code>01
</code></pre>

<p>outpoint</p>

<pre><code>3abe215f943956b8020b55669facbdbf74929b7877475994de5195827a36e45900000000
</code></pre>

<p>script len</p>

<pre><code>6c
</code></pre>

<p>push immediate 73 bytes</p>

<pre><code>49
</code></pre>

<p>bytes</p>

<pre><code>3046022100ee238cad1e8ac7f14661760b1b1fb2cf171f41afb31e3b59d3ced2284a1c2a71022100bef7fb989ccfb00a65c009a77b46bc818d2e80458668f73da0072966aaa28b6201
</code></pre>

<p>push immediate 33 bytes</p>

<pre><code>21
</code></pre>

<p>bytes</p>

<pre><code>03b2abe09a1c4e67c3eb9acd5596452a5d785c6e5a772fbea9a29ca95c15598ea6
</code></pre>

<p>sequence</p>

<pre><code>ffffffff
</code></pre>

<p>(Everything below is part of the outputs.)</p>

<pre><code>0206cfbb9f0f0000001976a914a66ba35c1d9bdcc8dfeb0fb8bedb16e1a570487d88ac09165612000000001976a914b420350a7b274e059d7ba5c97e8887d447b7287588ac00000000
</code></pre>

CC BY-SA 3.0
2017-04-01T02:05:22.663Z
Yeah, he's looking at already disassembled data. Not at the full script in hex.
Pieter Wuille
CC BY-SA 3.0
2017-04-01T11:03:02.590Z
The public key is a point wich has two 32b numbers, but this unknown data has only one number. There is no mistake, because I look at this data on the block explorer sites and it's the same as in my question.
Denis Leonov
CC BY-SA 3.0
2017-04-01T17:40:56.353Z
@Denis This is a compressed key, which is a single 32b number and a single bit. See https://bitcoin.org/en/glossary/compressed-public-key and http://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key
Nick ODell
CC BY-SA 3.0
2017-04-01T18:03:17.217Z
@NickODell as I understand compressed key is the X coordinate of uncompressed key?
Denis Leonov
CC BY-SA 3.0
2017-04-01T18:04:58.710Z
@Denis Yeah, that's right. See http://davidederosa.com/basic-blockchain-programming/elliptic-curve-keys/ for how to compress it.
Nick ODell
CC BY-SA 3.0
2017-03-31T22:17:45.873Z
2017-04-01T18:07:14.483Z
2017-04-01T18:07:14.483Z
Nick ODell
<p>There are many untypical <code>Input script</code> data in blockchain. What does it mean?</p>

<p>For example, transaction:</p>

<p><code>4A253F17E5F4B24B41F72A6AE46DD1BCB25F7F33769C2AA5D50C6A6A7CF9F76E</code> (<a href="https://blockchain.info/en/tx/4a253f17e5f4b24b41f72a6ae46dd1bcb25f7f33769c2aa5d50c6a6a7cf9f76e" rel="nofollow noreferrer">link</a>)</p>

<p>has it's input script:</p>

<p><code>3046022100EE238CAD1E8AC7F14661760B1B1FB2CF171F41AFB31E3B59D3CED2284A1C2A71022100BEF7FB989CCFB00A65C009A77B46BC818D2E80458668F73DA0072966AAA28B620103B2ABE09A1C4E67C3EB9ACD5596452A5D785C6E5A772FBEA9A29CA95C15598EA6</code></p>

<p>When I trying to parse this raw data, the result is:</p>

<p><code>30</code></p>

<p><code>46</code></p>

<p><code>02</code></p>

<p><code>21</code></p>

<p><code>00EE238CAD1E8AC7F14661760B1B1FB2CF171F41AFB31E3B59D3CED2284A1C2A71</code> – Sig r</p>

<p><code>02</code></p>

<p><code>21</code></p>

<p><code>00BEF7FB989CCFB00A65C009A77B46BC818D2E80458668F73DA0072966AAA28B62</code> – Sig s</p>

<p><code>01</code></p>

<p><code>03</code></p>

<p><code>B2ABE09A1C4E67C3EB9ACD5596452A5D785C6E5A772FBEA9A29CA95C15598EA6</code> – <strong>Unknown data</strong>.</p>

<p>What is the unknown data? This is not a Public Key, but what is it?</p>

<p>P.S. I checked that this unknown data is not a part of public key (X coordinate of Public Key as I thinking). After calculating Y coordinate (on EC) of Public Key I get <code>9F203515694856269C76C797D8E8E784EBDB927B650705E348F6FBA07DC56FAF</code>. After I check the signature (Sig) with this: </p>

<p><code>Public Key = B2ABE09A1C4E67C3EB9ACD5596452A5D785C6E5A772FBEA9A29CA95C15598EA6, 9F203515694856269C76C797D8E8E784EBDB927B650705E348F6FBA07DC56FAF</code></p>

<p><code>Transaction hash for this Sig = 59E4367A829551DE94594777789B9274BFBDAC9F66550B02B85639945F21BE3A</code>.</p>

<p>Then I calculate <code>x</code> and <code>y</code> from <code>Public Key</code>, <code>Hash</code> and generator point <code>G</code>. But <code>x</code> does not match the <code>Sig r</code> from raw data. So this way did not working.</p>

<bitcoin-core><script><raw>
Untypical input script
Denis Leonov
# Untypical input script

(Asked by: username_0 on 2017-03-31)

There are many untypical `Input script` data in blockchain. What does it mean?

For example, transaction:

`4A253F17E5F4B24B41F72A6AE46DD1BCB25F7F33769C2AA5D50C6A6A7CF9F76E` ([link](https://blockchain.info/en/tx/4a253f17e5f4b24b41f72a6ae46dd1bcb25f7f33769c2aa5d50c6a6a7cf9f76e))

has it's input script:

`3046022100EE238CAD1E8AC7F14661760B1B1FB2CF171F41AFB31E3B59D3CED2284A1C2A71022100BEF7FB989CCFB00A65C009A77B46BC818D2E80458668F73DA0072966AAA28B620103B2ABE09A1C4E67C3EB9ACD5596452A5D785C6E5A772FBEA9A29CA95C15598EA6`

When I trying to parse this raw data, the result is:

`30`

`46`

`02`

`21`

`00EE238CAD1E8AC7F14661760B1B1FB2CF171F41AFB31E3B59D3CED2284A1C2A71` – Sig r

`02`

`21`

`00BEF7FB989CCFB00A65C009A77B46BC818D2E80458668F73DA0072966AAA28B62` – Sig s

`01`

`03`

`B2ABE09A1C4E67C3EB9ACD5596452A5D785C6E5A772FBEA9A29CA95C15598EA6` – **Unknown data**.

What is the unknown data? This is not a Public Key, but what is it?

P.S. I checked that this unknown data is not a part of public key (X coordinate of Public Key as I thinking). After calculating Y coordinate (on EC) of Public Key I get `9F203515694856269C76C797D8E8E784EBDB927B650705E348F6FBA07DC56FAF`. After I check the signature (Sig) with this:

`Public Key = B2ABE09A1C4E67C3EB9ACD5596452A5D785C6E5A772FBEA9A29CA95C15598EA6, 9F203515694856269C76C797D8E8E784EBDB927B650705E348F6FBA07DC56FAF`

`Transaction hash for this Sig = 59E4367A829551DE94594777789B9274BFBDAC9F66550B02B85639945F21BE3A`.

Then I calculate `x` and `y` from `Public Key`, `Hash` and generator point `G`. But `x` does not match the `Sig r` from raw data. So this way did not working.

**Tags:** bitcoin-core, script, raw


---

## 1 answers

### Answer by username_1 on 2017-03-31. Score: 1 | Accepted answer

It is a public key. I think you're parsing this transaction incorrectly - what you should get is that there are two elements. The first is a signature, and 73 bytes long, starting with `3046022100ee238c...` The second element is a public key, and 33 bytes long, and starts with `03b2abe09a1c4e67...`

---

Here's the transaction you linked, broken up into sig and pubkey.

version

```
01000000

```

vin count

```
01

```

outpoint

```
3abe215f943956b8020b55669facbdbf74929b7877475994de5195827a36e45900000000

```

script len

```
6c

```

push immediate 73 bytes

```
49

```

bytes

```
3046022100ee238cad1e8ac7f14661760b1b1fb2cf171f41afb31e3b59d3ced2284a1c2a71022100bef7fb989ccfb00a65c009a77b46bc818d2e80458668f73da0072966aaa28b6201

```

push immediate 33 bytes

```
21

```

bytes

```
03b2abe09a1c4e67c3eb9acd5596452a5d785c6e5a772fbea9a29ca95c15598ea6

```

sequence

```
ffffffff

```

(Everything below is part of the outputs.)

```
0206cfbb9f0f0000001976a914a66ba35c1d9bdcc8dfeb0fb8bedb16e1a570487d88ac09165612000000001976a914b420350a7b274e059d7ba5c97e8887d447b7287588ac00000000

```

> **Comments:**
> **username_2**: Yeah, he's looking at already disassembled data. Not at the full script in hex.  
> **username_0**: The public key is a point wich has two 32b numbers, but this unknown data has only one number. There is no mistake, because I look at this data on the block explorer sites and it's the same as in my question.  
> **username_1**: @username_0 This is a compressed key, which is a single 32b number and a single bit. See https://bitcoin.org/en/glossary/compressed-public-key and http://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key  
> **username_0**: @username_1 as I understand compressed key is the X coordinate of uncompressed key?  
> **username_1**: @username_0 Yeah, that's right. See http://davidederosa.com/basic-blockchain-programming/elliptic-curve-keys/ for how to compress it.  

---

