When should I use Many to Many instead of Multi Sender?

Use Many to Many when each recipient should be funded by a specific source wallet inside the same batch. Use Multi Sender when one wallet should fund many recipients without per-row signers.

What format do imported rows have to use?

Source rows are privateKey,amount per line. Destination rows are wallet address per line. Pairs are matched by row order, so make sure both lists have the same length to avoid unpaired entries.

Can I transfer SOL and SPL together in one batch?

No. Each batch uses one asset type — either native SOL or one SPL mint. Run separate batches if you need to move both, since signers and fee accounting differ between them.

How are failed rows handled?

Invalid rows are flagged during validation before any transaction is signed. After execution, the per-row table shows the failed status, signature state, and error message so you can resolve and rerun only the affected pairs.

Are private keys stored by this tool?

No. Private keys live in the browser only for the duration of the run and are used to sign transactions client-side. They are not transmitted to a server or saved to local storage by the tool.

What happens if source and destination row counts differ?

The tool warns when one side has more rows than the other and only executes the matched pairs. Extra rows on either side are skipped, so balance sources and destinations before execution to avoid silent drops.

Many to Many Transfer

Send in matched pairs: every sender wallet pays its own recipient.

Wallet source

Connect wallet in top bar

Token

Enter a token mint address

Wallets

Pairs: 0Senders: 0Recipients: 0Valid: 0Ready: 0Total SOL: 0

Summary

Platform fee (0.001 × 0)0 SOL

Network fee~0 SOL

Total to send0 SOL

Private keys are used only in your browser to sign each transfer. They are never sent to a server.

About this tool

What it does

Sends paired transfers from many source wallets to many destination wallets in one batch. Each row is a from-to-amount pair, validated and previewed before signed execution from imported signers.

How it works

Paste or upload source rows with private keys and amounts and destination rows with addresses. The tool pairs them, validates inputs, shows a fee preview, then signs and sends each pair in sequence.

Why use it

Faster than running individual transfers when many wallets need to fund many recipients. Row-level validation, paired execution, SOL and SPL support, and one summary keep large payout batches consistent and reviewable.

How to run a many-to-many transfer in 3 steps

Pick the asset and import rows
Choose SOL or an SPL token, then paste or upload the source rows (privateKey + amount) and the destination rows. The tool validates lines and surfaces invalid or duplicate entries.
Review the pair preview
Check the paired source-to-destination table, total amounts, network fee estimate, and platform fee. Confirm pair counts match before continuing — extra rows on either side are not paired.
Execute the batch
Click execute to sign and send each pair sequentially. Watch the progress table for per-row status, signatures, and any failed transfers, then review the final batch result.

What is a many-to-many transfer on Solana?

A many-to-many transfer pairs N source wallets with N destination wallets so each source funds one specific recipient inside the same batch. It differs from Multi Sender, which sends from one wallet to many recipients, and from a one-to-one transfer because every row in the batch has its own signer. On Solana each pair becomes a separate signed transaction with its own network fee, so the cost scales linearly with the number of pairs and is shown in the summary panel before signing.

Key features

Paired source-to-destination row mapping in a single import flow
Paste or CSV upload — Source rows accept privateKey and amount; destination rows accept addresses
Row validation — Invalid private keys, malformed amounts, and duplicate addresses surface before execution
SOL and SPL support — Pick native SOL or any SPL token mint for the whole batch
Fee preview — Network and platform fees displayed per pair and as a batch total
Per-row execution table — Status, signature, and error visible for every pair as it runs
Sequential signing model — Each row uses its own signer so there is no shared sender bottleneck

What to do after

Multi Sender

Send from one wallet to many recipients when sources do not need to be paired

Batch Collector

Sweep dust and leftover balances back into a single consolidation wallet

Relay Transfer

Route a single transfer through configurable hops for added route control

Wallet Scope

Validate both sides of the pairing before you run the batch

Ready to run a many-to-many batch?

Import the source and destination rows, confirm pair counts and totals, then execute the batch to send each pair from its own signer in one coordinated run.

Frequently asked questions

Many to Many guideHow it works, step-by-step usage, and FAQs.Learn more

Many to Many Transfer

Send in matched pairs: every sender wallet pays its own recipient.

Wallet source

Connect wallet in top bar

Token

Enter a token mint address

Wallets

Pairs: 0Senders: 0Recipients: 0Valid: 0Ready: 0Total SOL: 0

Summary

Platform fee (0.001 × 0)0 SOL

Network fee~0 SOL

Total to send0 SOL

Private keys are used only in your browser to sign each transfer. They are never sent to a server.

About this tool

What it does

Sends paired transfers from many source wallets to many destination wallets in one batch. Each row is a from-to-amount pair, validated and previewed before signed execution from imported signers.

How it works

Paste or upload source rows with private keys and amounts and destination rows with addresses. The tool pairs them, validates inputs, shows a fee preview, then signs and sends each pair in sequence.

Why use it

How to run a many-to-many transfer in 3 steps

Pick the asset and import rows
Choose SOL or an SPL token, then paste or upload the source rows (privateKey + amount) and the destination rows. The tool validates lines and surfaces invalid or duplicate entries.
Review the pair preview
Check the paired source-to-destination table, total amounts, network fee estimate, and platform fee. Confirm pair counts match before continuing — extra rows on either side are not paired.
Execute the batch
Click execute to sign and send each pair sequentially. Watch the progress table for per-row status, signatures, and any failed transfers, then review the final batch result.

What is a many-to-many transfer on Solana?

Key features

Paired source-to-destination row mapping in a single import flow
Paste or CSV upload — Source rows accept privateKey and amount; destination rows accept addresses
Row validation — Invalid private keys, malformed amounts, and duplicate addresses surface before execution
SOL and SPL support — Pick native SOL or any SPL token mint for the whole batch
Fee preview — Network and platform fees displayed per pair and as a batch total
Per-row execution table — Status, signature, and error visible for every pair as it runs
Sequential signing model — Each row uses its own signer so there is no shared sender bottleneck

What to do after

Multi Sender

Send from one wallet to many recipients when sources do not need to be paired

Batch Collector

Sweep dust and leftover balances back into a single consolidation wallet

Relay Transfer

Route a single transfer through configurable hops for added route control

Wallet Scope

Validate both sides of the pairing before you run the batch

Ready to run a many-to-many batch?

Import the source and destination rows, confirm pair counts and totals, then execute the batch to send each pair from its own signer in one coordinated run.

Frequently asked questions

Many to Many guideHow it works, step-by-step usage, and FAQs.Learn more

Many to Many Transfer

What it does

How it works

Why use it

How to run a many-to-many transfer in 3 steps

Pick the asset and import rows

Review the pair preview

Execute the batch

What is a many-to-many transfer on Solana?

Key features

What to do after

Ready to run a many-to-many batch?

Frequently asked questions

When should I use Many to Many instead of Multi Sender?

What format do imported rows have to use?

Can I transfer SOL and SPL together in one batch?

How are failed rows handled?

Are private keys stored by this tool?

What happens if source and destination row counts differ?

Many to Many Transfer

What it does

How it works

Why use it

How to run a many-to-many transfer in 3 steps

Pick the asset and import rows

Review the pair preview

Execute the batch

What is a many-to-many transfer on Solana?

Key features

What to do after

Ready to run a many-to-many batch?

Frequently asked questions

When should I use Many to Many instead of Multi Sender?

What format do imported rows have to use?

Can I transfer SOL and SPL together in one batch?

How are failed rows handled?

Are private keys stored by this tool?

What happens if source and destination row counts differ?

You might like