01How Arbitrum charges for posting your list to Ethereum
Every Arbitrum transaction pays for 2 things: computation on Arbitrum, and posting the transaction's data to Ethereum (Arbitrum docs). Arbitrum converts the Ethereum part into extra gas units at the same gas price. So there is no separate fee line: you pay it all as gas, in ETH.
In a multisend, each recipient adds data to the transaction, so the Ethereum part grows with the list.
Even so, in a long list the Ethereum part is a small share of the gas. Per recipient, it is several times lower than for a separate transfer. The Ethereum part moves with the base fees of Ethereum and Arbitrum from block to block.
02400 wallets per transaction under Arbitrum's 32 million gas limit
Arbitrum One allows up to 32 million gas per transaction, a limit set by the ArbOS 51 upgrade, activated on January 8, 2026 (Arbitrum docs). The multisender's cap of 400 wallets per transaction is Tokenry's own setting on every EVM chain, not Arbitrum's limit. One review takes up to 10,000 recipients.
A transaction that pays ETH to 400 new wallets is estimated at under half of that limit.
When you send ETH or tokens to multiple addresses on Arbitrum and the list has more than 400 wallets, the transactions go out one after another. Your wallet shows each prompt after the previous transaction confirms. If only part of the list is paid, "Send the remaining N" runs a fresh review for the recipients not sent yet. You can also download them as a CSV and upload the file again.
03When one payout on an Arbitrum list is refused
The multisender skips a payout that the token refuses, or a payout to a wallet that refuses ETH. Its Tokenry fee comes back to you in the same transaction, its amount stays with you, and the rest of the list still goes through. For example, native USDC lets Circle block addresses, so a USDC payout to a blocked wallet is skipped.
A payout that would make the whole transaction fail must be removed in the review before you can confirm.
The review also marks recipients that are contracts, such as a DEX pool, because tokens sent to a contract can often never be moved again. A multisig on Ethereum may have no contract at the same address on Arbitrum One. Check that each multisig exists on Arbitrum One before you send (Safe docs).