Transaction Repeater

WHAT IT DOES

Transaction Repeater allows you to send the exact same transaction multiple times in a single operation. Specify a recipient address, value in ETH, optional data payload, gas limit, and a repeat count — the tool sends the transaction sequentially with incrementing nonces, ensuring each transaction is confirmed before the next is sent. This is essential for batch operations like sending payments to multiple recipients with identical amounts, stress testing smart contracts, executing repeated administrative actions, or automating workflows that require multiple identical transactions. The tool shows a live progress table with transaction hashes, confirmation status, block numbers, and actual gas costs using receipt.effectiveGasPrice for accurate post-EIP-1559 accounting.

HOW TO USE

Connect your wallet using the BGWallet bridge (MetaMask or any Web3 wallet). Ensure you are on the desired network — Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, or any EVM chain. Enter the recipient address, the amount of ETH to send per transaction (value), optional calldata (hex data for contract interactions), the gas limit, and the number of times to repeat the transaction (1-100). The review area shows the total value being sent and an estimated gas cost based on the current live gas price. Click "Send repeated transactions" to begin. The tool checks your balance covers the total cost, then sends each transaction sequentially, waiting for 1 confirmation between each. Results appear in a table with transaction hashes, status, block numbers, and actual gas costs.

TECHNICAL MECHANISM

The tool uses ethers.js to send raw transactions directly from your wallet signer. For each repeat, it constructs a transaction object with the same to, value, data, gasLimit, and gasPrice parameters. The nonce is automatically managed by the wallet — each subsequent transaction uses the next nonce, ensuring they are processed in order. The tool fetches the live gas price from the network using signer.getGasPrice() (not hardcoded) to ensure accurate fee estimation. Before sending, it calculates the total cost (value * count + gasPrice * gasLimit * count) and checks it against the wallet balance (PLAYBOOK-C §5.3). Each transaction is sent sequentially and awaited (PLAYBOOK-C §5.6) — sending them all at once would cause nonce conflicts. After each transaction mines, the tool reads the receipt and extracts the actual gas cost using receipt.effectiveGasPrice (PLAYBOOK-C §5.5), which accurately reflects the post-EIP-1559 fee market rather than the submitted gasPrice cap. Results are displayed with block confirmations and cost breakdowns.

WHAT IT CANNOT SEE

The tool cannot repeat transactions that depend on state changes between repeats — for example, if the first transaction transfers ownership of a contract to a new address, the second transaction (which calls the same function) will fail because the caller is no longer authorized. It cannot handle transactions that require different gas settings per repeat — all repeats use identical gas parameters. It cannot detect if a repeated transaction will fail due to state changes between sends — the failure is only discovered after each transaction is sent. It cannot repeat transactions across different chains — all repeats must be on the same network. It cannot simulate transactions before sending to predict failures. The tool does not use batch contracts — each transaction is sent individually from your wallet.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains (Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche C-Chain, Fantom, and others). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. Each transaction consumes gas and costs the sender. The tool uses the current gas price at the time of sending; gas price changes between repeats may affect costs. The tool does not store any data — all transactions are broadcast live. The tool is provided as-is with no warranty or liability. Always review the transaction details in your wallet before signing. For contract calls, ensure the data field contains properly encoded function calldata.