<p>There certainly is a rationale explanation- if you are manually constructing your own transactions i.e. you are writing your own code to create bitcoin transactions its pretty easy to do this by accident.</p>

<p>The reason this is so easy is because there is no explicit 'transaction fee' output, rather  transaction fee = total inputs - total outputs. Hence it is pretty easy to accidentally forget to e.g. send. the remainder back to yourself or to miscalculate the remainder.</p>

<p>I did this once when I was testing sending miner fees in some transaction code I was writing. I mistyped the conversion factor converting from BTC to satoshis (raw bitcoin transactions record amounts as satoshis - 64-bit unsigned integers), published the transaction, and ended up sending something like 10 BTC instead of 0.1 BTC to the miners.</p>

CC BY-SA 3.0
2013-06-25T21:35:45.237Z
2013-06-25T21:35:45.237Z
BitPiggy
<p>One possibility is that the transaction was injected by the same person who mined the block. Thus the same person who paid the fee collected the fee.</p>

CC BY-SA 3.0
2013-06-20T11:42:11.277Z
FWIW the block this transaction was included in was mined by the EclipseMC mining pool.
sourcenouveau
CC BY-SA 3.0
2013-12-15T20:39:12.083Z
I already heard about rumors saying that such of "mistakes" are in fact attempts to laundry stolen Bitcoins.
Jan Moritz
CC BY-SA 3.0
2013-06-20T07:45:00.480Z
2013-06-20T07:45:00.480Z
David Schwartz
<p>Hard to tell if it was intended or accidental, but <a href="http://blockchain.info/tx/1d7749c65c90c32f5e2c036217a2574f3f4403da39174626b246eefa620b58d9" rel="nofollow">there</a> <a href="http://blockchain.info/tx/098b3a9faeb2c6e5dc42878b9d0a1106d4aafce72c85d0eab54c384652e0bdbc" rel="nofollow">are</a> <a href="http://blockchain.info/tx/13dffdaef097881acfe9bdb5e6338192242d80161ffec264ee61cf23bc9a1164" rel="nofollow">many</a> <a href="http://blockchain.info/tx/1dbd420f23f8ac58b994c7b84f8667670dfcad39ec9f34e555a0c6281b7e2c04" rel="nofollow">other</a> <a href="http://blockchain.info/tx/b9032a5eb76ca8b8b13163157278264d534377cf9885fad981df7b02174ea550" rel="nofollow">transactions</a> out there that have very high fees.</p>

CC BY-SA 3.0
2013-06-20T10:42:53.907Z
2013-06-20T10:42:53.907Z
jgm
<p>What's also possible is that someone mistakenly swapped the sending amount and the transaction fee amount. I almost did that with the bockchain.info wallet but luckily noticed it in the confirmation screen.</p>

<p>In this case, he could have intended a fee of 0.02314796 BTC and tried to send 2.7 BTC to the address. The other 65+ BTC could be just change.</p>

CC BY-SA 3.0
2013-06-20T08:12:21.527Z
2013-06-20T08:12:21.527Z
Steven Roose
<p>I noticed a 2417 byte <a href="http://blockchain.info/tx/8f1fae55831a87e5f0180a85f9c4583cfc524170bf0826a495289de98927f232">transaction</a> with a 2.7 BTC transaction fee. Is there any rational explanation for this, or was it perhaps a mistake?</p>

<transaction-fees>
Anomalous 2.7 BTC transaction fee observed
sourcenouveau
# Anomalous 2.7 BTC transaction fee observed

(Asked by: username_0 on 2013-06-20)

I noticed a 2417 byte [transaction](http://blockchain.info/tx/8f1fae55831a87e5f0180a85f9c4583cfc524170bf0826a495289de98927f232) with a 2.7 BTC transaction fee. Is there any rational explanation for this, or was it perhaps a mistake?

**Tags:** transaction-fees


---

## 4 answers

### Answer by username_5 on 2013-06-20. Score: 3 | Accepted answer

What's also possible is that someone mistakenly swapped the sending amount and the transaction fee amount. I almost did that with the bockchain.info wallet but luckily noticed it in the confirmation screen.

In this case, he could have intended a fee of 0.02314796 BTC and tried to send 2.7 BTC to the address. The other 65+ BTC could be just change.


---

### Answer by username_1 on 2013-06-25. Score: 2

There certainly is a rationale explanation- if you are manually constructing your own transactions i.e. you are writing your own code to create bitcoin transactions its pretty easy to do this by accident.

The reason this is so easy is because there is no explicit 'transaction fee' output, rather transaction fee = total inputs - total outputs. Hence it is pretty easy to accidentally forget to e.g. send. the remainder back to yourself or to miscalculate the remainder.

I did this once when I was testing sending miner fees in some transaction code I was writing. I mistyped the conversion factor converting from BTC to satoshis (raw bitcoin transactions record amounts as satoshis - 64-bit unsigned integers), published the transaction, and ended up sending something like 10 BTC instead of 0.1 BTC to the miners.


---

### Answer by username_2 on 2013-06-20. Score: 1

One possibility is that the transaction was injected by the same person who mined the block. Thus the same person who paid the fee collected the fee.

> **Comments:**
> **username_0**: FWIW the block this transaction was included in was mined by the EclipseMC mining pool.  
> **username_3**: I already heard about rumors saying that such of "mistakes" are in fact attempts to laundry stolen Bitcoins.  

---

### Answer by username_4 on 2013-06-20. Score: 0

Hard to tell if it was intended or accidental, but [there](http://blockchain.info/tx/1d7749c65c90c32f5e2c036217a2574f3f4403da39174626b246eefa620b58d9) [are](http://blockchain.info/tx/098b3a9faeb2c6e5dc42878b9d0a1106d4aafce72c85d0eab54c384652e0bdbc) [many](http://blockchain.info/tx/13dffdaef097881acfe9bdb5e6338192242d80161ffec264ee61cf23bc9a1164) [other](http://blockchain.info/tx/1dbd420f23f8ac58b994c7b84f8667670dfcad39ec9f34e555a0c6281b7e2c04) [transactions](http://blockchain.info/tx/b9032a5eb76ca8b8b13163157278264d534377cf9885fad981df7b02174ea550) out there that have very high fees.


---

