Read a transaction

1Find the transaction

A transaction is known by its transaction ID, or txid: 64 letters and digits that your wallet shows after a send. Open the explorer for your network:

Paste into the box that says Search by block, tx, or address... and press Enter. The explorer decides what you typed by its shape:

You can also go straight to a transaction by adding its txid to the address: …/explorer2/tx/ followed by the txid.

2Unconfirmed, 1/6, Confirmed

The badge at the top right of the page tells you how settled the payment is. Each new block on top of the one holding your transaction adds one confirmation.

The count is the latest block height minus the transaction's block height, plus one. Our sweep below sat in block 360879. When the newest block was 360880, the badge read 360880 − 360879 + 1 = 2/6.

We watched two testnet payments, reloading the page every 15 seconds. Times are UTC:

Both took about five minutes. Divi aims for one block a minute, but the gaps vary. The sweep went straight from Unconfirmed to 2/6 because two blocks came three seconds apart, and then waited over three minutes for the third.

3The top of the page

This is the 10 tDIVI payment as the explorer showed it, one block after it was made:

Transaction Details                      1/6
TXID         9b0cdbadb1fa7a30...a2744e1182897ed1   Copy
Block        #360835   d5b80d58...7ec39b7a
Time         10/22/2026, 6:46:22 AM
Size         226 B
Total Output 99.9999774 DIVI

• TXID is shortened in the middle. Use Copy to get all 64 characters.
• Block is the block height and the start and end of the block's hash. Both open the block. The row appears only once a block holds the transaction.
• Time is the time written into that block, shown in your own computer's time zone. Our browser was on New York time, so the block's 10:46:22 UTC showed as 6:46:22 AM. It is not the moment you pressed Send.
• Size is the transaction's size in bytes. The fee depends on it, not on the amount.
• Total Output adds up every output, including the change that went back to the sender. It is not the amount that was paid.

4Inputs, outputs, change and the fee

Under the summary are two lists. Inputs are the coins being spent, each with the address that held it. Outputs are where the coins go. Every address opens its own page.

1 Input
#0  yC7cys...jeaiXK   100.00 DIVI
2 Outputs
#0  xvzMd5...DbiRyc   10.00 DIVI
#1  y5JZKX...yZpGuQ   89.9999774 DIVI

A wallet spends whole coins, the way you hand over a banknote. Here the sender's wallet held one coin of 100 tDIVI. Output #0 is the payment of 10. Output #1 is the change: it went back to a new address in the sender's own wallet. The explorer does not say which output is change. Only the sender's wallet knows which addresses are its own.

There is no Fee row. The fee is what goes in but does not come out:

fee = inputs − outputs
    = 100.00 − (10.00 + 89.9999774)
    = 0.0000226 DIVI

The test send in Send DIVI works the same way: 24,798.49988 in, 1.00 and 24,797.49985 out, so the fee was 0.00003. Nobody receives the fee. Since Divi switched to proof of stake, the network destroys it.

5Transactions that look different

A sweep has no change. We emptied a test wallet into one address. Three coins went in and one output came out:

3 Inputs
#0  xynZNy...HpEUVr   0.4999228 DIVI
#1  yC7cys...jeaiXK   1.00 DIVI
#2  yFqyEt...2zTAks   88.9999548 DIVI
1 Output
#0  yJehBf...nFLjY4   90.4998165 DIVI

The inputs add up to 90.4998776, so the fee was 0.0000611. It cost more than the payment above because three inputs make a bigger transaction: 486 bytes against 226.

Every block today starts with two special transactions. They create the new coins. We opened the first two transactions in block 360879:

In proof of stake the first transaction is empty. The reward comes in the second: a staker spends its own coin and gets it back with more on top. Here the output is 166 DIVI larger than the input, so the subtraction for the fee gives a negative number. That gap is the new coins, not a fee. The nonstandard 0.00 output is an empty marker, not a payment to anyone.

6The address page

Click any address to see everything it has done. This is the address that got the 10 tDIVI:

xvzMd5vNjhdYw3Z42RizxfgD1mr4DbiRyc
Balance          10.00 DIVI
Total Received   10.00 DIVI
                 Everything ever sent to this address
Transaction History (1)    CSV  Cards  Ledger

• Balance is what the address holds now.
• Total Received never goes down. After the wallet spent this coin, the balance fell to 0 but Total Received stayed at 10.00. Your wallet may count differently: see Receive your first DIVI.
• Transaction History lists each transaction with From and To. Cards and Ledger are two views of the same list. CSV downloads all of it as a spreadsheet file.
• Raw Transaction Data is the node's own record, for people who want every detail. blocktime is the Time row in seconds since 1970. baretxid is a second ID that leaves out the signatures. Search and share the txid, not the baretxid.

Troubleshooting

No information available about transaction. The explorer cannot find that txid. Check that you copied all 64 characters and that you are on the right network's explorer. A send the network refused never appears at all: see Send DIVI.

No results found for "…". The search was 64 characters but matched no block or transaction. The same checks apply.

It stays Unconfirmed. Reload the page after a minute or two. If it is still not in a block after ten minutes, the amount may be too small. Send DIVI explains what to do.

The Time is hours away from when I sent it. The explorer shows the block's time in your computer's time zone. Compare it with your local clock, not with UTC.

Total Output is far bigger than what I sent. It includes your change. Look at the outputs one by one.

Still stuck? Ask the Divi chatbot, or see all tutorials.

← Send DIVI Avoid scams →