<p>That transaction is 90 KB in size; presumably the exchange is aggregating deposit transactions from many customers.  And its fee is about 1.3 satoshis per byte.  As you can see <a href="https://bitcoinfees.earn.com/" rel="nofollow noreferrer">here</a>, there are currently lots of outstanding transactions offering a higher fee rate; as such, a miner would likely prefer to confirm 90 KB worth of smaller and more lucrative transactions, rather than this one.</p>

<p>The output address type doesn't have any direct effect on confirmation time or miner preference, as far as I know.</p>

<p>The size of the mempool in MB is not a particularly useful statistic in estimating confirmation time (until it gets below the block size, at which point you would roughly expect that the next block will confirm everything).  Transactions don't get confirmed first-come-first-served; a low-fee transaction can languish indefinitely as long as more higher-fee transactions continue to arrive and be given priority.</p>

<p>Note that as a customer, this is not your problem.  Your job was done once your deposit transaction was confirmed, and the exchange should have credited your account at that point.   What they do with the money after that is solely their concern.  It's quite possible that they've intentionally lowballed the fee.  If a lull in transactions occurs sometime soon, maybe they get lucky and it confirms at this low fee.  Maybe they don't care whether this happens anytime soon; after all, it's probably just money moving around inside their organization.  If at some point it becomes more urgent, they can offer a higher fee (e.g. using RBF or CPFP).  But none of that is any concern of yours.</p>

CC BY-SA 4.0
2018-09-11T23:08:07.987Z
2018-09-11T23:08:07.987Z
Nate Eldredge
<p>I made a deposit into a bitcoin exchange on 2018-09-11 06:57:41. The exchange then made a withdrawal transaction on 2018-09-11 13:19.</p>

<p>The time is now 2018-09-11 21:55 but the transaction still has not had any confirmations. The mempool size is currently 12 Mb which should not be large enough to cause such a delay.</p>

<p>The output for the withdrawal is a bech32 address. Has anyone else seen delays in withdrawal transactions, possibly to do with different address formats on the output?</p>

<p><a href="https://blockchair.com/bitcoin/transaction/946d199348cdd21209e1c42f8df1700be9a238bb220d7e03ceff5b136e7cca2b" rel="nofollow noreferrer">https://blockchair.com/bitcoin/transaction/946d199348cdd21209e1c42f8df1700be9a238bb220d7e03ceff5b136e7cca2b</a></p>

<p>Thanks</p>

<transactions><bitcoin-core>
Withdrawal transaction made 8 hours ago still has not had any confirmations
Stephen Thompson
# Withdrawal transaction made 8 hours ago still has not had any confirmations

(Asked by: username_0 on 2018-09-11)

I made a deposit into a bitcoin exchange on 2018-09-11 06:57:41. The exchange then made a withdrawal transaction on 2018-09-11 13:19.

The time is now 2018-09-11 21:55 but the transaction still has not had any confirmations. The mempool size is currently 12 Mb which should not be large enough to cause such a delay.

The output for the withdrawal is a bech32 address. Has anyone else seen delays in withdrawal transactions, possibly to do with different address formats on the output?

<https://blockchair.com/bitcoin/transaction/946d199348cdd21209e1c42f8df1700be9a238bb220d7e03ceff5b136e7cca2b>

Thanks

**Tags:** transactions, bitcoin-core


---

## 1 answers

### Answer by username_1 on 2018-09-11. Score: 0 | Accepted answer

That transaction is 90 KB in size; presumably the exchange is aggregating deposit transactions from many customers. And its fee is about 1.3 satoshis per byte. As you can see [here](https://bitcoinfees.earn.com/), there are currently lots of outstanding transactions offering a higher fee rate; as such, a miner would likely prefer to confirm 90 KB worth of smaller and more lucrative transactions, rather than this one.

The output address type doesn't have any direct effect on confirmation time or miner preference, as far as I know.

The size of the mempool in MB is not a particularly useful statistic in estimating confirmation time (until it gets below the block size, at which point you would roughly expect that the next block will confirm everything). Transactions don't get confirmed first-come-first-served; a low-fee transaction can languish indefinitely as long as more higher-fee transactions continue to arrive and be given priority.

Note that as a customer, this is not your problem. Your job was done once your deposit transaction was confirmed, and the exchange should have credited your account at that point. What they do with the money after that is solely their concern. It's quite possible that they've intentionally lowballed the fee. If a lull in transactions occurs sometime soon, maybe they get lucky and it confirms at this low fee. Maybe they don't care whether this happens anytime soon; after all, it's probably just money moving around inside their organization. If at some point it becomes more urgent, they can offer a higher fee (e.g. using RBF or CPFP). But none of that is any concern of yours.


---

