How to Transfer SUI Tokens Between Two Sui Wallet Accounts

Understanding SUI Token Transfer Mechanics

1. SUI tokens exist as individual objects on the Sui blockchain, not as balances in accounts. Each coin carries its own unique identifier and version number.

2. Transferring SUI requires referencing a specific coin object ID rather than simply specifying an amount from a balance pool.

3. The sender must possess full ownership of the coin object being transferred — no shared or delegated control is permitted for standard transfers.

4. Every transfer triggers a state change recorded immutably on-chain, visible via Sui Explorer using the transaction digest.

5. Unlike EVM chains, gas fees are paid in SUI but do not consume the transferred amount — they are deducted separately from the sender’s available coin objects.

Prerequisites for a Valid Transfer

1. Both sender and recipient must have active Sui wallet extensions installed and unlocked in a Chromium-based browser.

2. The sender must hold at least one SUI coin object with sufficient balance to cover both the transfer amount and gas fees.

3. The recipient’s wallet address must be a valid 32-byte Sui address beginning with 0x and formatted without spaces or special characters.

4. Network configuration must point to the correct Sui RPC endpoint — mainnet, testnet, or devnet — matching the environment where the coins reside.

5. No pending transactions should block the sender’s latest object version; concurrent modifications may cause version conflicts.

Step-by-Step Transfer Execution

1. Open the Sui wallet extension and unlock it using the stored password.

2. Click the Send button located on the wallet dashboard interface.

3. Paste the recipient’s full Sui address into the designated field labeled Recipient Address.

4. Enter the exact quantity of SUI to send, ensuring decimal precision aligns with SUI’s 9-digit scale (e.g., 1.5 SUI = 1500000000).

5. Review the pre-filled gas estimation and confirm that the sender’s selected coin object meets the required amount after gas deduction.

6. Click Confirm Transaction, then approve the signature request in the wallet popup.

7. Wait for finality confirmation — typically under 2 seconds — and verify the updated balance and transaction history within the wallet UI.

Handling Common Transfer Failures

1. Insufficient Gas Coin: The wallet fails to locate a coin object with enough SUI to cover both transfer and gas. Solution: Manually split a larger coin using the Split Coin tool before initiating transfer.

2. Invalid Recipient Address: Input contains non-hexadecimal characters or incorrect length. Solution: Re-copy the address directly from the recipient’s wallet Receive screen.

3. Object Version Mismatch: Attempted transfer uses an outdated coin object version due to prior mutation. Solution: Refresh wallet data or re-select the coin object after recent activity.

4. Network Timeout: RPC connection drops during submission. Solution: Switch to a different public RPC endpoint or check current network status on official Sui dashboards.

Frequently Asked Questions

Q: Can I cancel a SUI transfer after signing but before finality?A: No. Once signed and submitted, the transaction enters the consensus pipeline and cannot be revoked or reversed.

Q: Do I need to manually specify which coin object to send?A: Not always. The wallet auto-selects eligible coins by default, but advanced users can override this selection using the Choose Coin option before confirming.

Q: Why does my wallet show multiple SUI coin objects after a single transfer?A: Sui automatically splits leftover amounts into new coin objects. For example, sending 1.2 SUI from a 5 SUI coin creates two new objects: one for 1.2 SUI and another for the remaining 3.8 SUI.

Q: Is there a minimum transfer amount enforced by the protocol?A: The Sui protocol imposes no minimum. However, practical limits arise from gas costs — transfers smaller than the gas fee will fail.