Skip to content
Open J Tools
Relay Transfer 0.00023 SOL per hop Platform fee Open tool

Relay Transfer

Relay Transfer moves SOL or an SPL token from one source to a destination by hopping it through a chain of freshly generated intermediate wallets. You set how many hops, how long to wait between each, and whether to add a priority fee.

Relay Transfer j.tools/en/tools/relay-transfer

Open tool

Platform fee

0.00023 SOL per hop

Network fee, rent and transaction value are separate.

When this tool fits

#when-this-tool-fits
  • You want to route funds through a configurable number of hops, with delays between them, instead of one direct send.
  • You want the run signed with no wallet popup at all, which is what Local Signer (private key) mode is for.
  • You need per-hop progress, signatures, and error tracking, plus a recovery file of the generated wallets.

Before you start

#before-you-start
  • A source. Either your connected wallet (Wallet), or a private key entered under Local Signer. Wallet mode handles SOL only. SPL relays require Local Signer.
  • A valid destination wallet address. The field validates it live as you type.
  • An amount above zero, and for an SPL relay, the token’s mint address (pick it with the built-in token selector).
  • Enough SOL for the route. In Wallet mode your wallet pays the amount plus every hop’s network and priority fee, and the platform fees come out of the amount along the way. In Local Signer mode the source pays the amount plus its own hop fee, and each relay wallet pays its hop fee out of what it forwards. Either way the destination receives less than you send. SPL relays need meaningfully more, because each relay wallet is pre-seeded with SOL for its fees and token-account rent. The SPL vs Token-2022 note explains why token transfers carry that account overhead.

Use only short-lived operational wallets; never enter a seed phrase or a long-term wallet key.

How to use it

#how-to-use-it
  1. Set asset, amount and destination

    Choose the wallet source: Wallet for a SOL relay from your connected wallet, or Local Signer with a private key. Select SOL, or pick an SPL token with the token selector. Enter the amount and paste the final wallet address as the destination.

  2. Configure relay depth and timing

    Choose how many intermediate wallets to route through, with a preset, the slider, or a typed number. Pick a fixed delay or a random delay between hops, from 0 to 120 seconds, and an optional priority fee.

  3. Execute and watch the hops

    Check the summary: relay count, hop count, send amount, estimated destination amount, network fee, platform fee, and total cost. Click Execute Relay Transfer. The recovery .xlsx downloads first, then the hops run one after another and each one fills a row in the progress table.

Key settings

#key-settings
  • Token type: SOL or SPL. SOL drains each hop down to zero on the way forward. SPL seeds each relay wallet with SOL for fees, then forwards the token amount unchanged.
  • Token mint: Required for SPL. The mint of the token to relay, chosen from your wallet’s token list or pasted into the token picker. Ignored for SOL.
  • Amount: What passes through the path. For SOL it is the amount before fees; for SPL it is the per-hop token amount. MAX (Wallet mode, SOL only) fills your balance minus every hop’s network and priority fee, and keeps a little over 0.001 SOL in your wallet.
  • Destination wallet: The final wallet that receives the last hop. Validated as a Solana public key as you type.
  • Relay count: How many intermediate wallets to route through. Presets up to 2500, slider up to 2500, custom entry up to 5000. Total hops equal relay count plus one.
  • Delay mode: Fixed waits a set number of seconds between hops; random samples a wait between a minimum and maximum. Keep each value between 0 and 120 seconds: Local Signer refuses a run with a longer delay. No delay runs after the final hop.
  • Priority fee: A validator tip applied per transaction: None, Normal, Fast, Express, or Custom. Default is None.
  • Source mode: Wallet signs the first hop in your connected wallet (one approval), then the generated relay keys sign the later hops in the browser. Local Signer signs every hop locally with no wallet popup. Wallet mode is SOL-only. No hop is sponsored: each transaction’s network fee is paid by the wallet that signs it.

Fees and costs

#fees-and-costs
CostAmount
J Tools platform fee0.00023 SOL per hop
Solana network feePaid to validators during the transaction; shown in the live summary.
Rent and transaction valueShown separately when required; not part of the platform fee.

How to use it

  1. Set asset, amount and destination
  2. Configure relay depth and timing
  3. Execute and watch the hops

How it works

Funds hop through fresh wallets one transaction per hop

  1. Fresh relay wallets generated relay × N
  2. Their keys saved to a recovery file .xlsx
  3. 0.00023 SOL platform fee per hop 0.00023 SOL
  4. Source checked for amount plus its fees principal + fees
  5. SPL: each relay seeded with SOL first fees + rent
  6. Your wallet or key signs hop 1 hop 1
  7. Each relay key signs the next hop hop n+1
  8. Delay of 0 to 120 seconds between hops fixed · random

Last hop lands in the destination wallet hops = relays + 1

Relay Transfer · circles are the steps in How to use it, squares the steps in How it works

Before you sign

#before-you-sign

Check the live summary before signing. The app is the current source of truth for amount, fee and route.

Common issues

#common-issues
  • Not enough source SOL. Before the first hop, the source must cover the amount plus its fees: every hop’s network fee in Wallet mode, its own hop fee in Local Signer mode. A source that would be left with a balance above zero but below the rent-exempt minimum is refused too. Top up, or send a little less or everything. SPL relays need more, since each relay wallet is seeded for fees and account rent; an underfunded source throws an insufficient-balance error.
  • A hop failed mid-run. The chain stops at the first failure and the later hops do not run. The funds rest in the last wallet that received them, which is the source if the first hop failed. On an SPL relay, the SOL seeded into the later relay wallets stays there too. Recover them using the downloaded .xlsx. The tool does not auto-retry or auto-recover.
  • Amount too small for the chain. Every relay wallet is new, so each one has to receive at least the rent-exempt minimum, and each hop peels off its fees. The page shows Minimum for this chain under the amount; stay above it, or use fewer relays.
  • SPL relay blocked in Wallet mode. Wallet mode is SOL-only. Switch to Local Signer for SPL.
  • Lost the recovery file. If a run is mid-flight or a hop failed, the keys in that file are the only way to reach stranded funds. It holds the generated relay wallets, not your source key, and there is no server-side copy to restore from.

Practical tips

#practical-tips
  • Start shallow, then scale. A small depth costs little and tells you whether the timing and cost behave the way you expect. Raise the relay count once you trust the path.
  • Mind the runtime. Every hop is a separate transaction with its own fee and any delay you set, so a deep run with long random delays can take a while. The summary’s hop count is the quickest way to gauge total time and cost.
#related-tools

Help

#help

The tool on this page

Relay Transfer

j.tools/en/tools/relay-transfer

Platform fee
0.00023 SOL per hop
Network fee, rent and transaction value are separate.
Open tool