Batched transactions let you send an asset to many recipients in a single on-chain transaction, instead of creating a separate transaction for each recipient. You provide the recipients in the destinations array of the standard create transaction API call, and Fireblocks builds one transaction that pays all of them.
The capability is available across the main chain families that support it: EVM networks, Solana, and UTXO based assets such as Bitcoin. The core concept is the same everywhere. The details, such as supported assets, fee handling, and limits, differ per chain and are covered in the chain specific articles linked below.
Why use Batched transactions
- Lower fees: one transaction carries a single on-chain footprint and one set of metadata, so it is more cost-effective than sending one transaction per recipient. Savings grow with the number of recipients.
- Atomicity: all transfers in a batch settle together. Either the whole transaction succeeds or none of it does, so you never end up with a partially completed payout run.
- Fewer approvals and signatures: the batch is approved once through your Policy and signed once, instead of once per recipient.
- Operational simplicity: one transaction to track, reconcile, and report on, instead of many.
Common use-cases
- Payroll and contractor payouts
- Partner, distributor, and affiliate payouts
- Treasury distributions and rebalancing
- Token airdrops and reward programs
- High-volume withdrawal and distribution flows
How it works
- You call the standard create transaction endpoint and pass a destinations array, where each entry has an amount and a destination.
- Fireblocks constructs a single transaction that pays every destination in the array.
- Each batch sends a single asset. To send different assets, submit a separate batch per asset.
- The transaction is approved and signed once, then broadcast as a single on-chain transaction.
Good to know
- API only: batched transactions are created through the API. In the Console they appear in transaction history labeled Multi-destination.
- Limits vary by chain: the maximum number of recipients and other constraints depend on the network. See each chain-specific article for details.
- On some chains, fees can be paid by the source vault directly or sponsored by a relay vault (gasless). Availability depends on the chain.
Chain-specific guides
For implementation details, supported assets, limits, and examples, see the guide for your chain: