1Before you send
A transaction cannot be cancelled or pulled back once a block includes it. Check three things first:
- The address. Paste it, never type it. Read the first letter:
Dfor real DIVI,xoryfor testnet. Compare the first four and last four characters with what the receiver sent you. Receive your first DIVI explains why. - The amount. It is in DIVI, not in your own currency. The smallest unit is a duff, one hundred-millionth of a DIVI.
- The network. Your wallet must be on the same network as the address. Practise on testnet, where the coins have no value.
2The fee
The fee is destroyed. Nobody receives it, not even the staker who makes the block. It depends on the size of the transaction in bytes, not on the amount, so sending 1 DIVI and sending 24,800 DIVI cost about the same. Each wallet picks it differently:
| Wallet | How it sets the fee | What we paid |
|---|---|---|
| C++ Divi node (also inside Divi Desktop and BoxWallet) | 0.0001 DIVI per 1,000 bytes | 0.0000226 for 225 bytes |
| IronDivi node | A fixed 0.00001, plus 0.00001 per coin spent and 0.000005 per output | 0.00003 with one coin spent, 0.00004 with two |
| Web wallet | A Fee box, 0.0001 to start, which you can change. It refuses a fee above 1 DIVI. | not sent in this test |
| Browser extension | A Fee box, 0.00005 to start, which you can change | not sent in this test |
Most sends also have a change output. Your wallet spends whole coins, so it pays the rest back to an address of its own, the way a shop hands back change. You will see that second output on the explorer. It is still your money.
3Send a small test first
Before a large payment, send a small amount to the same address. Then check it on the explorer, or ask the receiver to confirm it arrived. If the address was wrong, you lost the test amount and nothing more. The extra fee is tiny.
- Send a small amount, such as 1 DIVI.
- Open the transaction on Explorer 2.0 and check the receiving address in the Outputs list.
- Wait for at least one confirmation, shown as 1/6, and for the receiver to say it arrived.
- Send the rest.
On testnet our 1 tDIVI test send was in a block 30 seconds later. Explorer 2.0 showed it like this:
Transaction Details 1/6 Block #360857 Size 226 B 1 Input #0 yEgUT5...kQ2UM4 24,798.49988 DIVI 2 Outputs #0 yJehBf...nFLjY4 1.00 DIVI #1 yDNAyv...96WDoW 24,797.49985 DIVI
Output #0 is the payment. Output #1 is the change, back to a new address in our own wallet. The fee is what is missing: 24,798.49988 − 1 − 24,797.49985 = 0.00003. Read a transaction explains every field.
4IronDivi node
You need coins in the wallet from Create your first wallet. IronDivi spends only coins with at least one confirmation. If the wallet is encrypted, unlock it first. The passphrase goes in on standard input, so it never appears in your shell history:
$ read -s P; printf '%s\n300\n' "$P" | irondivi-cli -c ~/divi-test/irondivi.conf --stdin walletpassphrase; unset P $ irondivi-cli -c ~/divi-test/irondivi.conf getblockcount 360856 $ irondivi-cli -c ~/divi-test/irondivi.conf sendtoaddress yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4 1 5e027c70aab09bef14d6997f2eaf8835b4b6f9010dfd7fb47ea4a93ee79b81d7
The long answer is the transaction ID, or txid. Paste it into the explorer to follow the payment. To see the change, list the coins that have no confirmation yet:
$ irondivi-cli -c ~/divi-test/irondivi.conf listunspent 0 0
[
{
"address": "yDNAyvkDCkjY8piRrYk2VsWokoqT96WDoW",
"amount": 24797.49985,
"confirmations": 0,
"ischange": true,
…
}
]
getblockcount go up by one, about a minute, and then lock. A wallet restored from your recovery phrase gets the key back if this happens.
$ irondivi-cli -c ~/divi-test/irondivi.conf getblockcount
360857
$ irondivi-cli -c ~/divi-test/irondivi.conf walletlock
$ irondivi-cli -c ~/divi-test/irondivi.conf validateaddress yDNAyvkDCkjY8piRrYk2VsWokoqT96WDoW
{
…
"hdkeypath": "m/44'/301'/0'/1/8",
"ismine": true,
"iswatchonly": false,
…
}
"ismine": true after the lock means the key was kept. Our main send of 24,800 tDIVI spent two coins and cost 0.00004. It went through the same steps.
To check what a send cost, ask for the transaction. IronDivi puts the fee inside the amount:
$ irondivi-cli -c ~/divi-test/irondivi.conf gettransaction 5e027c70aab09bef14d6997f2eaf8835b4b6f9010dfd7fb47ea4a93ee79b81d7
{
"amount": -1.00003,
…
"fee": -0.00003,
…
}
5C++ Divi command line
The same command works on the C++ node. A locked wallet answers:
error code: -13 error message: Error: Please enter the wallet passphrase with walletpassphrase first.
After you unlock it, send:
$ divi-cli -testnet sendtoaddress yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4 1
2d9659f92ac0a107f70f08338842b69be8cf994c135a5de67db4879556f360c7
$ divi-cli -testnet walletlock
$ divi-cli -testnet gettransaction 2d9659f92ac0a107f70f08338842b69be8cf994c135a5de67db4879556f360c7
{
"amount": -1.0000226,
"fee": 2.26e-05,
…
"details": [
{
"address": "yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4",
"category": "send",
"amount": -1.0,
"vout": 1,
"fee": -2.26e-05
}
]
}
The fee was 0.0000226 DIVI for 225 bytes. The C++ node keeps a pool of ready keys, so you can lock it straight after a send: its change address was still its own after the lock. It also refuses an address from the other network with Invalid DIVI address, which IronDivi does not.
6Divi Desktop and BoxWallet
Divi Desktop: we did not run it for this page, so we do not describe its screens. It runs the C++ node, so its fee and checks are the ones in section 5, and sendtoaddress works in its debug console.
BoxWallet runs the C++ node too. Its README (release v0.8.38, read 2026-10-22) describes a Send panel: "Destination and amount, with a review step before anything is broadcast". Read the review step closely: it is your last chance to catch a wrong address.
7Web wallet, browser extension and Telegram
| Wallet | How to send |
|---|---|
| Web wallet | Press Send. Fill in Recipient Address, Amount and Fee (Max sends everything), then press Send Transaction. A Confirm send sheet shows the network, recipient, amount, network fee and total. Press Confirm & Send. On mainnet the sheet has a red MAINNET banner and the button says Send real DIVI. When it is done you see Sent! TX: and the start of the txid. |
| Browser extension | Press Send. Fill in To Address, Amount (MAX sends everything) and Fee, then Continue. The Confirm Send screen shows To, Amount, Fee and Total. Type your password under Enter Password to Sign and press Send. |
| Telegram wallet | /send <address> <amount> [memo] prepares the payment. You confirm it in the wallet app, which holds your keys. The bot cannot send on its own. |
The web wallet and the extension both refuse an address from the wrong network. The web wallet says Invalid recipient address. The extension says which first letter it expected.
8Amounts that are too small
The network refuses a payment output under 0.0000546 DIVI. That limit is called dust: an output so small it would cost more in fees to spend than it is worth. We tried it on testnet:
| Wallet | Sending 0.00001 or less |
|---|---|
| C++ Divi node | Refused at once: Transaction output(s) amount too small. Exactly 0.0000546 went through. |
| IronDivi 0.2.6 | Accepted, and gave a txid. The rest of the network never took it, so it never reached a block or the explorer. The coin it spent stayed stuck as pending until we restarted the node. |
If an IronDivi send never shows on the explorer, stop and start the node. The stuck send is dropped and the coin is spendable again. The web wallet and the extension do not check the amount either, so keep every payment above 0.0000546 DIVI.
Troubleshooting
error code: -13. The wallet is locked. Unlock it as in section 4.
IronDivi says Insufficient funds. Have … DIVI, need … DIVI (code -6), but the wallet has enough. IronDivi spends only confirmed coins. Wait for the last payment in to reach one confirmation.
Invalid DIVI address. A letter is wrong, or the address is for the other network. Copy it again from the receiver.
The send does not show on the explorer after a few minutes. Check the amount against section 8. On IronDivi, restart the node to free the coin.
The change address shows as watch-only in IronDivi. The wallet was locked before the next block. Restore from your phrase as in Create your first wallet.
Still stuck? Ask the Divi chatbot, or see all tutorials.