user137501: The output:




Block Height
TXID
Output Index
Satoshi Amount
Locking Script
Status




211914
AF32BB06F12F2AE5FDB7FACE7CD272BE67C923E86B7A66A76DED02D954C2F94D
0
100000000
aa20000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f87
Unspent




user137501: Upon inspecting the hash we can observe that it matches the hash of Bitcoin's genesis block: 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f.
However, the hash is in the wrong byte order, so the genesis block header can't be used to unlock it, and whomever created it had permanently burned his 1 Bitcoin because the reversed-byte hash has some unknown preimage which will likely never be discovered, so no, it is not spendable.
There is another output, with the correct byte order:




Block Height
TXID
Output Index
Satoshi Amount
Locking Script
Status




211997
A4BFA8AB6435AE5F25DAE9D89E4EB67DFA94283CA751F393C1DDC5A837BBC31B
0
100000000
aa206fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d619000000000087
Spent




which was successfully spent by using Bitcoin's genesis block header as input script:
4c500100000000000000000000000000000000000000000000000000000000000000000000003ba3edfd7a7b12b27ac72c3e67768f617fc81bc3888a51323a9fb8aa4b1e5e4a29ab5f49ffff001d1dac2b7c


137501: <p>The output:</p>
<div class="s-table-container">
<table class="s-table">
<thead>
<tr>
<th>Block Height</th>
<th>TXID</th>
<th>Output Index</th>
<th>Satoshi Amount</th>
<th>Locking Script</th>
<th>Status</th>
</tr>
</thead>
<tbody>
<tr>
<td>211914</td>
<td>AF32BB06F12F2AE5FDB7FACE7CD272BE67C923E86B7A66A76DED02D954C2F94D</td>
<td>0</td>
<td>100000000</td>
<td>aa20000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f87</td>
<td>Unspent</td>
</tr>
</tbody>
</table>
</div> 137501: <p>Upon inspecting the hash we can observe that it matches the hash of Bitcoin's genesis block: <a href="https://blockchair.com/bitcoin/block/0" rel="nofollow noreferrer"><code>000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f</code></a>.</p>
<p>However, the hash is in the wrong byte order, so the genesis block header can't be used to unlock it, and whomever created it had permanently burned his 1 Bitcoin because the reversed-byte hash has some unknown preimage which will likely never be discovered, so no, it is not spendable.</p>
<p>There is another output, with the correct byte order:</p>
<div class="s-table-container">
<table class="s-table">
<thead>
<tr>
<th>Block Height</th>
<th>TXID</th>
<th>Output Index</th>
<th>Satoshi Amount</th>
<th>Locking Script</th>
<th>Status</th>
</tr>
</thead>
<tbody>
<tr>
<td>211997</td>
<td>A4BFA8AB6435AE5F25DAE9D89E4EB67DFA94283CA751F393C1DDC5A837BBC31B</td>
<td>0</td>
<td>100000000</td>
<td>aa206fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d619000000000087</td>
<td>Spent</td>
</tr>
</tbody>
</table>
</div>
<p>which was successfully <a href="https://explorer.viawallet.com/btc/tx/a4bfa8ab6435ae5f25dae9d89e4eb67dfa94283ca751f393c1ddc5a837bbc31b" rel="nofollow noreferrer">spent</a> by using Bitcoin's genesis block header as input script:</p>
<pre><code>4c500100000000000000000000000000000000000000000000000000000000000000000000003ba3edfd7a7b12b27ac72c3e67768f617fc81bc3888a51323a9fb8aa4b1e5e4a29ab5f49ffff001d1dac2b7c
</code></pre>
