<p>Perhaps this is due to the "malleability attack" that was going on; it can be that the transaction has gone through with a different transaction ID.  It would be easier if you disclose the input and/or output address.</p>

CC BY-SA 3.0
2015-10-09T20:14:29.210Z
2015-10-09T20:14:29.210Z
tobixen
<p>wondering if anyone can help me.  I moved funds from one wallet to another with transaction 582386d5b5480804535cf382727ab72b9a09dd1435b3444f18c20617d3198a65.  Fees were dutifully paid by my wallet.  I've never had a transaction take more than an hour or two to confirm if fees are paid.  Says it spent unconfirmed inputs?  Anyone know what it is, and how to get my money back if it does not confirm?</p>

<p>Thanks much!</p>

CC BY-SA 3.0
2015-10-09T20:06:02.500Z
blockchain.info now says "Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database."
tobixen
<transactions><unconfirmed-transactions>
Unconfirmed Transaction - Paid Fees
foreverimmortal
# Unconfirmed Transaction - Paid Fees

(Asked by: username_0 on 2015-10-09)

wondering if anyone can help me. I moved funds from one wallet to another with transaction 582386d5b5480804535cf382727ab72b9a09dd1435b3444f18c20617d3198a65. Fees were dutifully paid by my wallet. I've never had a transaction take more than an hour or two to confirm if fees are paid. Says it spent unconfirmed inputs? Anyone know what it is, and how to get my money back if it does not confirm?

Thanks much!

**Tags:** transactions, unconfirmed-transactions

> **Comments:**
> **username_1**: blockchain.info now says "Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database."  

---

## 1 answers

### Answer by username_1 on 2015-10-09. Score: 0

Perhaps this is due to the "malleability attack" that was going on; it can be that the transaction has gone through with a different transaction ID. It would be easier if you disclose the input and/or output address.


---

