<p>You could add an extra output with a locking script that uses <a href="https://en.bitcoin.it/wiki/OP_RETURN" rel="nofollow noreferrer">OP_RETURN</a> to embed an arbitrary timestamp.</p>
<p>Obviously this increases the size and therefore likely increases the cost in required transaction fee to get the transaction confirmed promptly.</p>
<p>This would be time of transaction creation, not time of confirmation.</p>
<hr />
<p>Related:</p>
<ul>
<li><a href="https://bitcoin.stackexchange.com/q/29554/13866">Explanation of what an OP_RETURN transaction looks like</a></li>
</ul>

CC BY-SA 4.0
2022-06-30T11:17:10.940Z
2022-06-30T11:17:10.940Z
RedGrittyBrick
<ol>
<li>Would it be possibile to add additional  information in TX?</li>
</ol>
<p>I would like to add time of transaction in it.</p>
<ol start="2">
<li>Would hash of TX change if hostile node would change that time ?</li>
</ol>

<transactions><nodes><mempool>
Additional instructions in TX
W M
# Additional instructions in TX

(Asked by: username_0 on 2022-06-30)

1. Would it be possibile to add additional information in TX?

I would like to add time of transaction in it.

2. Would hash of TX change if hostile node would change that time ?

**Tags:** transactions, nodes, mempool


---

## 1 answers

### Answer by username_1 on 2022-06-30. Score: 1

You could add an extra output with a locking script that uses [OP\_RETURN](https://en.bitcoin.it/wiki/OP_RETURN) to embed an arbitrary timestamp.

Obviously this increases the size and therefore likely increases the cost in required transaction fee to get the transaction confirmed promptly.

This would be time of transaction creation, not time of confirmation.

---

Related:

* [Explanation of what an OP\_RETURN transaction looks like](https://bitcoin.stackexchange.com/q/29554/13866)


---

