Transaction Details
Tx hash
200fdca17aa85515642e765bc20aebf61931c9d887ac49ee19d6f8f16e7016f9
Tx prefix hash
829b0c0a50f560baedf9064f06a46f90fb0ed51c1cd72bfdb689100d948af737
Tx public key
19d95eebf33a43fc5ff3a13621e987be58dcf1d91ae516decc1395cb777bab66
Age [y:d:h:m:s]
04:255:15:00:14
Timestamp [UCT] (epoch)
2019-10-18 21:24:10 (1571433850)
Block
288438 (1204630 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0119d95eebf33a43fc5ff3a13621e987be58dcf1d91ae516decc1395cb777bab66032100d68bd81c61b3cecf7f87e9bb7bd8dc3446c1d784b640d40158aed9b1999cb939021b0000000000000000000000000047225d5900000000000000000000
Outputs
1 output(s) for total of 20.047181770 ARQ
stealth address amount amount idx
00: 95175c2f574ccca92f53d1441b15a24daf8ce517d67ab46d9ff596f4aa95b4a3 20.047181770 1300830 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 288456, 
  "vin": [ {
      "gen": {
        "height": 288438
      }
    }
  ], 
  "vout": [ {
      "amount": 20047181770, 
      "target": {
        "key": "95175c2f574ccca92f53d1441b15a24daf8ce517d67ab46d9ff596f4aa95b4a3"
      }
    }
  ], 
  "extra": [ 1, 25, 217, 94, 235, 243, 58, 67, 252, 95, 243, 161, 54, 33, 233, 135, 190, 88, 220, 241, 217, 26, 229, 22, 222, 204, 19, 149, 203, 119, 123, 171, 102, 3, 33, 0, 214, 139, 216, 28, 97, 179, 206, 207, 127, 135, 233, 187, 123, 216, 220, 52, 70, 193, 215, 132, 182, 64, 212, 1, 88, 174, 217, 177, 153, 156, 185, 57, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 71, 34, 93, 89, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}