SEQUENTIAL USDC DISTRIBUTION

Many payouts,one motion.

Arc / PAYMENT RAIL

Recipient lists are divided into atomic Arc transactions of up to 100 transfers. Local checkpoints keep every run visible and resumable.

≤100PER TX
AUTOBATCH
LOCALRESUME
RUN / COMPOSE

Payment ledger

Waiting for wallet connection

Enter at least two Arc addresses and test USDC amounts. The run is split into sequential transactions of at most 100 recipients; each transaction is independently atomic.

UTF-8 / recipient,amount / 2+ rows / up to 1.25 MB
LOCAL / PAYMENT LEDGER

Transaction history

Runs are stored only in this browser and origin. Recipient addresses and amounts are local, but they are not encrypted.

Loading local history…
No local runs yet.

Your first submitted batch will appear here with its progress.

PROTOCOL / HOW IT WORKS

One list becomes a sequence of verified moves.

BatchPayArc plans the full list locally, simulates every chunk, and asks your wallet to sign one transaction at a time. Each finalized receipt is checked against the expected USDC Transfer events before the next chunk can start.

Read the full flow
01 / ENTRY CONTRACT

Multicall3From

0x522fAf9A91c41c443c66765030741e4AaCe147D0

Receives aggregate3 and preserves the connected EOA as the sender of every USDC subcall.

02 / PAYMENT ASSET

USDC ERC-20

0x3600000000000000000000000000000000000000

Executes each 6-decimal transfer. The same underlying USDC balance also pays Arc gas through its native interface.

NON-CUSTODIALYour private key and recovery phrase never leave the wallet.

SAFE CHECKPOINTSA submitted hash is reconciled before any retry is considered.

ArcScan Explorer