Current offer: 25% off eligible service fees.
Current offer: 25% off eligible service fees.
Route tokens through intermediate wallets to sever direct transaction records between the sender and receiver. Ideal for sensitive asset transfers, it completely blocks tracing pathways and enhances the stealth of on-chain fund flows.
Import source private keys in bulk and enter the initial amount for each relay chain.
No data yet. Choose a method to add addresses.
Recipient N is strictly paired with sender N. Rows are never reordered.
No data yet. Choose a method to add addresses.
Choose the relay-wallet count for each chain, then download and confirm the generated backup.
Use the download icon to generate and save the relay wallets
Confirm each hop through the active RPC, or use Jito Bundle when available.
Choose a preset tip or enter a custom SOL amount. The component outputs lamports for transaction builders.
SOL
The next step checks addresses, amounts, and estimated fees without sending transactions.
The lowest service fee network-wide, each address costs only
Need help? View the full SOL Relay Transfer tutorial, or contact us.
The SOL Relay Transfer tool routes SOL from a source wallet to a final recipient through one or more generated relay wallets. CiaoTool automatically creates and executes the complete transfer path based on the source, recipient, and selected number of relays. This tool currently supports native SOL only and does not transfer SPL tokens.Q2: How are source wallets matched with final recipients? Source wallets and final recipients are matched row by row in the order they are imported. The first source wallet routes SOL to the first recipient through its own relay path, the second source wallet routes SOL to the second recipient, and so on. CiaoTool does not rearrange the pairs automatically. Make sure both lists contain the same number of entries and verify every address and amount before submission.Q3: When should I use SOL Relay Transfer? It is suitable for multi-wallet fund allocation, operational wallet separation, internal treasury transfers, moving funds between purpose-specific wallets, and situations where a direct transaction between the source and final recipient is not preferred. Relay wallets add intermediate steps to the transfer path, but every wallet and transaction remains publicly recorded on Solana.Q4: Does Relay Transfer make on-chain transactions untraceable? No. Relay Transfer reduces the direct transaction link between the source wallet and final recipient, but it does not delete or conceal on-chain records. Every transfer hop, relay address, amount, and timestamp remains publicly recorded on Solana. Third parties may still analyze transfer timing, amounts, wallet behavior, and other on-chain data. The tool does not guarantee anonymity or untraceable transactions.Q5: How many relay wallets can I use? You can configure the number of relay wallets used for each transfer path. More relay wallets create additional transfer hops and increase the transaction count, Solana network costs, platform fees, and processing time. The available range and estimated final amount are displayed on the operation page.
Relay wallets temporarily receive and forward SOL. If the task is interrupted by a network error or failed transaction, some funds may remain in a relay wallet. Relay private keys are generated locally in the browser and are not stored or recoverable by CiaoTool. You must download and securely store the wallet backup before execution to retain access to any funds left in a relay address.
Each source wallet must sign the first outgoing transaction in its relay path. A standard browser wallet cannot automatically sign for multiple independent source addresses, so source wallet private keys are required for local batch signing. Use wallets dedicated to batch operations and test the complete relay process with a small amount of SOL first.
Source wallet private keys are used only to build and sign transactions locally in the browser. They are not uploaded, transmitted, or stored on CiaoTool servers. Relay wallets and their private keys are also generated locally. Related data is cleared when the page is closed or refreshed. Use a trusted device and store the relay wallet backup in a secure offline location.
RPC mode sends each transfer hop through the selected Solana RPC according to its confirmation dependencies. The next hop is processed after the previous transaction is confirmed. Jito mode submits the applicable transactions through Jito and requires a Jito tip. The execution method, estimated transaction count, and costs are displayed before confirmation.
If a task is interrupted or partially fails, avoid blindly restarting it. Review the transaction records and identify the relay address holding the remaining SOL. Import the corresponding private key from the downloaded relay wallet backup, then use a standard transfer or CiaoTool Multi-to-One Transfer to move the SOL into a wallet you control. Keep the backup until every path is complete and all balances are verified.
Route tokens through intermediate wallets to sever direct transaction records between the sender and receiver. Ideal for sensitive asset transfers, it completely blocks tracing pathways and enhances the stealth of on-chain fund flows.
Import source private keys in bulk and enter the initial amount for each relay chain.
No data yet. Choose a method to add addresses.
Recipient N is strictly paired with sender N. Rows are never reordered.
No data yet. Choose a method to add addresses.
Choose the relay-wallet count for each chain, then download and confirm the generated backup.
Use the download icon to generate and save the relay wallets
Confirm each hop through the active RPC, or use Jito Bundle when available.
Choose a preset tip or enter a custom SOL amount. The component outputs lamports for transaction builders.
SOL
The next step checks addresses, amounts, and estimated fees without sending transactions.
The lowest service fee network-wide, each address costs only
Need help? View the full SOL Relay Transfer tutorial, or contact us.
The SOL Relay Transfer tool routes SOL from a source wallet to a final recipient through one or more generated relay wallets. CiaoTool automatically creates and executes the complete transfer path based on the source, recipient, and selected number of relays. This tool currently supports native SOL only and does not transfer SPL tokens.Q2: How are source wallets matched with final recipients? Source wallets and final recipients are matched row by row in the order they are imported. The first source wallet routes SOL to the first recipient through its own relay path, the second source wallet routes SOL to the second recipient, and so on. CiaoTool does not rearrange the pairs automatically. Make sure both lists contain the same number of entries and verify every address and amount before submission.Q3: When should I use SOL Relay Transfer? It is suitable for multi-wallet fund allocation, operational wallet separation, internal treasury transfers, moving funds between purpose-specific wallets, and situations where a direct transaction between the source and final recipient is not preferred. Relay wallets add intermediate steps to the transfer path, but every wallet and transaction remains publicly recorded on Solana.Q4: Does Relay Transfer make on-chain transactions untraceable? No. Relay Transfer reduces the direct transaction link between the source wallet and final recipient, but it does not delete or conceal on-chain records. Every transfer hop, relay address, amount, and timestamp remains publicly recorded on Solana. Third parties may still analyze transfer timing, amounts, wallet behavior, and other on-chain data. The tool does not guarantee anonymity or untraceable transactions.Q5: How many relay wallets can I use? You can configure the number of relay wallets used for each transfer path. More relay wallets create additional transfer hops and increase the transaction count, Solana network costs, platform fees, and processing time. The available range and estimated final amount are displayed on the operation page.
Relay wallets temporarily receive and forward SOL. If the task is interrupted by a network error or failed transaction, some funds may remain in a relay wallet. Relay private keys are generated locally in the browser and are not stored or recoverable by CiaoTool. You must download and securely store the wallet backup before execution to retain access to any funds left in a relay address.
Each source wallet must sign the first outgoing transaction in its relay path. A standard browser wallet cannot automatically sign for multiple independent source addresses, so source wallet private keys are required for local batch signing. Use wallets dedicated to batch operations and test the complete relay process with a small amount of SOL first.
Source wallet private keys are used only to build and sign transactions locally in the browser. They are not uploaded, transmitted, or stored on CiaoTool servers. Relay wallets and their private keys are also generated locally. Related data is cleared when the page is closed or refreshed. Use a trusted device and store the relay wallet backup in a secure offline location.
RPC mode sends each transfer hop through the selected Solana RPC according to its confirmation dependencies. The next hop is processed after the previous transaction is confirmed. Jito mode submits the applicable transactions through Jito and requires a Jito tip. The execution method, estimated transaction count, and costs are displayed before confirmation.
If a task is interrupted or partially fails, avoid blindly restarting it. Review the transaction records and identify the relay address holding the remaining SOL. Import the corresponding private key from the downloaded relay wallet backup, then use a standard transfer or CiaoTool Multi-to-One Transfer to move the SOL into a wallet you control. Keep the backup until every path is complete and all balances are verified.