<p>There is none that I'm aware of, but technically speaking, the blockchain and the transaction hash would suffice to find it. It might be nice to add the block height number as well.</p>

<p>Something like:</p>

<pre><code>Tx 35779d11b2c5aedc1ada50aaa33aafb53ccc07dae71e6d18a35a0ccb872a0efa, Bitcoin Block 342508 
</code></pre>

<p>Would work as a citation.</p>

CC BY-SA 3.0
2015-02-09T05:10:41.493Z
That what I was leaning towards.  However I would lead with the chain and add the self reported date (but not time) base on UTC.

> Bitcoin, Transaction ID 35779d11b2c5aedc1ada50aaa33aafb53ccc07dae71e6d18a35a0ccb872a0efa, Block 342598, 7 Feb 2015
shemnon
CC BY-SA 3.0
2015-02-08T04:51:23.990Z
2015-02-08T04:51:23.990Z
Jimmy Song
<p>When writing an academic style paper where specific bitcoin transactions are used as examples, is there a standard format to "cite" a bitcoin transaction?  </p>

<p>If not, what do you think an appropriate format would be?  What data should be included?  What about altcoin chains, what would be different for those chains?</p>

<transactions><address><block><academic-research>
Correct Citation Format for a Bitcoin Transaction
shemnon
# Correct Citation Format for a Bitcoin Transaction

(Asked by: username_0 on 2015-02-07)

When writing an academic style paper where specific bitcoin transactions are used as examples, is there a standard format to "cite" a bitcoin transaction?

If not, what do you think an appropriate format would be? What data should be included? What about altcoin chains, what would be different for those chains?

**Tags:** transactions, address, block, academic-research


---

## 1 answers

### Answer by username_1 on 2015-02-08. Score: 2

There is none that I'm aware of, but technically speaking, the blockchain and the transaction hash would suffice to find it. It might be nice to add the block height number as well.

Something like:

```
Tx 35779d11b2c5aedc1ada50aaa33aafb53ccc07dae71e6d18a35a0ccb872a0efa, Bitcoin Block 342508 

```

Would work as a citation.

> **Comments:**
> **username_0**: That what I was leaning towards.  However I would lead with the chain and add the self reported date (but not time) base on UTC.  > Bitcoin, Transaction ID 35779d11b2c5aedc1ada50aaa33aafb53ccc07dae71e6d18a35a0ccb872a0efa, Block 342598, 7 Feb 2015  

---

