For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content

"Too large cluster" error on Bitcoin transactions

A Bitcoin transaction can fail with the status Failed to broadcast and an error that mentions too-large-cluster. The network refused it. Nothing moved, and the reserved balance returns to the account.

Why it happens

A transaction that spends coins from unconfirmed transactions is linked to them in a cluster. Bitcoin nodes refuse any transaction that takes its cluster over 64 transactions or 101 kvB.

The usual cause is large incoming transactions, such as deposit sweeps, sent with a very low fee. They stay unconfirmed, and withdrawals that spend their coins go over the limit. Withdrawals that spend only confirmed coins still succeed.

A retry will likely fail again. Pause withdrawals from the account until the incoming transactions confirm. To check, look for incoming transactions with 0 confirmations on the account.

How to solve it

  • Wait. When fees drop, the incoming transactions confirm and the problem clears. This can take hours or days.

  • Ask the sender to raise the fee (Replace-By-Fee). If the transactions come from your own systems, raise the fee there.

  • Boost a pending transaction of yours that spends a stuck incoming transaction. This is Child Pays For Parent: open its Transaction Details, click Boost, and set a custom fee in sat/vB. The fee must cover the parent's size too, so it can be far above the recommended rate. For example, a 250 vB child of a 34,000 vB parent at 1 sat/vB needs about 550 sat/vB to reach 5 sat/vB overall. Click Finalize and approve as usual.

Important: Do not ask the sender to replace a transaction that one of your pending transactions spends. Your pending transaction would be dropped.

Prevent it

Send deposit sweeps and other large consolidations at a fee rate that matches the network, not the minimum.

Need help?

Raise a ticket on the Service Desk with the ID of the failed transaction and the hashes of the unconfirmed incoming transactions.

Sources:

Last updated