Multi-wallet transfer
Match each sending wallet with its own recipient. Row one sends to row one, row two to row two, and so on. Each pair signs from its source wallet and sends in its own transaction.
Prepare
Each private key is paired with the recipient address on the same row. Row one sends to row one, row two to row two, and so on.
Import a pair list
One pair per row: private key, recipient, and an optional amount. You can still review every row after importing.
Blank = BNB
Sending wallets (private keys)
One private key per line. Keys are used only for local signing in this tab.
Receiving address
One address per line. Each address is paired with the private key on the same row.
Sending wallets: 0
Recipient addresses: 0
Fees：0.0005 BNB / per wallet
Multi-wallet multisender — send from many wallets to many addresses
A multi-wallet multisender matches each sending wallet with its own recipient. That makes it different from the usual multisender, where one wallet pays a whole list. Import a paired CSV, set an amount for each pair, then review balances, fees and the exact wallet-to-recipient mapping before anything is signed. Every pair is signed by its source wallet; when a platform fee applies, the transfer and fee are bundled into one transaction from that wallet.
- Wallet pairing
- Row one sends to row one; every source has its own recipient
- Amounts
- Fixed, full balance, reserved balance, random range or a custom amount per pair
- Signing
- Private keys stay in the browser tab and are used for local signing only
- Pacing
- Run up to five source wallets together, or wait a fixed or random interval between pairs
How it works
1. Import or paste the wallet pairs
Use one private key and one recipient per row. You can paste the two lists separately, upload a paired CSV, or start from the template. Duplicate source wallets and recipients are removed before sending.
2. Choose the asset and amount mode
Leave the token address blank to send the chain’s native coin, or enter an ERC-20 contract. Each pair can send a fixed amount, its full balance, a balance with funds held back, a random amount, or a custom amount entered in the table.
3. Check every balance and pair
The review screen reads each source wallet’s balance and flags pairs that cannot cover the transfer, the platform fee or gas. It also shows the total, expected gas and every wallet-to-recipient row before you sign.
4. Send, then retry only what remains
With no interval, up to five source wallets run together. With an interval, the next pair starts after the previous transaction confirms. Failed or interrupted pairs can be retried without resending pairs that already confirmed, and the full result can be exported as a CSV.
FAQ
How is this different from a normal multisender?
A normal multisender sends from one wallet to a list of recipients. A multi-wallet multisender pairs every sending wallet with its own recipient, so each payout comes from a different source address.
Are my private keys uploaded?
No. Keys stay in memory in the current browser tab and are used to sign locally. They are not uploaded and are not saved as a form draft.
Do I need to approve ERC-20 tokens?
Only when a source wallet does not already have enough allowance for the multicall contract. That approval is signed by the same source wallet and is skipped when the allowance is sufficient. Native coin transfers never need an approval.
What happens if one transfer fails?
The other pairs continue, and the result table shows which pairs succeeded, failed or never ran. Use the retry button to send only the remaining pairs; confirmed transfers are left alone.
Can the same wallet appear more than once?
No. Reusing one source wallet would create competing nonces when pairs run together. Use the regular single-wallet multisender when one wallet should pay several recipients.