<p>A is the data required by OP_CHECKSIG
B is the final witness component</p>
<p>Neither are part of the inscription, they are parts of the normal transaction in which the inscription is lurking.</p>

CC BY-SA 4.0
2024-02-22T19:05:05.970Z
Thanks. Appreciate it.
paranoid
CC BY-SA 4.0
2024-02-22T18:46:59.227Z
2024-02-22T18:46:59.227Z
RedGrittyBrick
<p><em>A</em> and <em>B</em> are not part of the inscription. <em>A</em> is a pubkey contained in the leaf script which is used to check the signature provided in the first witness item, <em>B</em> is the control block containing the leaf version and internal key. Also see: <a href="https://bitcoin.stackexchange.com/a/111396/5406">https://bitcoin.stackexchange.com/a/111396/5406</a></p>

CC BY-SA 4.0
2024-02-22T19:03:38.813Z
Thank you for answering my question.
paranoid
CC BY-SA 4.0
2024-02-22T18:54:42.963Z
2024-02-22T19:44:10.697Z
2024-02-22T19:44:10.697Z
Murch
<p>I am interested in Ordinals transactions' raw hexadecimal format. The example transaction I'm using is TXID: 6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799. There are some parts of the witness section of this transaction data that I cannot comprehend.</p>
<pre><code>&quot;5503&quot; # 853 bytes
&quot;20&quot; # 32 bytes
&quot;4a3ca2cf35f7902df1215f823d977df1174048b062e03a44f71c2ee736a60cc5&quot; # (A)
&quot;ac&quot; # OP_CHECKSIG
&quot;00&quot; # OP_FALSE 
&quot;63&quot; # OP_IF
&quot;03&quot; # 3 bytes
&quot;6f7264&quot; # &quot;ord&quot;
&quot;0101&quot; # N/A N/A
&quot;09&quot; # 9 bytes
&quot;696d6167652f706e67&quot; # &quot;image/png&quot;
&quot;00&quot; # OP_FALSE
&quot;4d&quot; # OP_PUSHDATA2
&quot;0802&quot; # 520 bytes =&gt; maximum value
&lt;skipping the following 520 bytes of image data&gt;
&quot;4d&quot; # OP_PUSHDATA2
&quot;1101&quot; # 273 bytes
&lt;skipping the following 273 bytes of the rest of the image data&gt;
&quot;68&quot; # OP_ENDIF
&quot;21&quot; # 33 bytes
&quot;c04a3ca2cf35f7902df1215f823d977df1174048b062e03a44f71c2ee736a60cc5&quot; # (B)
&quot;00000000&quot; # locktime &amp; end of entire transaction data
</code></pre>
<p>Can somebody tell me what (A) and (B) represent?</p>

<transactions><ordinals>
Parsing Ordinals Transaction, the inscribed data part
paranoid
# Parsing Ordinals Transaction, the inscribed data part

(Asked by: username_0 on 2024-02-22)

I am interested in Ordinals transactions' raw hexadecimal format. The example transaction I'm using is TXID: 6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799. There are some parts of the witness section of this transaction data that I cannot comprehend.
"5503" # 853 bytes
"20" # 32 bytes
"4a3ca2cf35f7902df1215f823d977df1174048b062e03a44f71c2ee736a60cc5" # (A)
"ac" # OP_CHECKSIG
"00" # OP_FALSE 
"63" # OP_IF
"03" # 3 bytes
"6f7264" # "ord"
"0101" # N/A N/A
"09" # 9 bytes
"696d6167652f706e67" # "image/png"
"00" # OP_FALSE
"4d" # OP_PUSHDATA2
"0802" # 520 bytes => maximum value

"4d" # OP_PUSHDATA2
"1101" # 273 bytes

"68" # OP_ENDIF
"21" # 33 bytes
"c04a3ca2cf35f7902df1215f823d977df1174048b062e03a44f71c2ee736a60cc5" # (B)
"00000000" # locktime & end of entire transaction data

Can somebody tell me what (A) and (B) represent?

**Tags:** transactions, ordinals


---

## 2 answers

### Answer by username_1 on 2024-02-22. Score: 1

A is the data required by OP\_CHECKSIG
B is the final witness component

Neither are part of the inscription, they are parts of the normal transaction in which the inscription is lurking.

> **Comments:**
> **username_0**: Thanks. Appreciate it.  

---

### Answer by username_2 on 2024-02-22. Score: 1

*A* and *B* are not part of the inscription. *A* is a pubkey contained in the leaf script which is used to check the signature provided in the first witness item, *B* is the control block containing the leaf version and internal key. Also see: <https://bitcoin.stackexchange.com/a/111396/5406>

> **Comments:**
> **username_0**: Thank you for answering my question.  

---

