Transaction Details
Tx hash
347c838f234237f7ae1769c68240eb20360d72c4a6d0f8e3b53dc07330110cdc
Tx prefix hash
1c3d15ad3434c5be891b6970e6c54e663a8c2c8dfb122885126d35bce7a8e4a0
Tx public key
b0e4bc7ac09a4a3fda0e3356ec5ec59692b9709fbfd34e7e3fd750a6dc04f172
Age [y:d:h:m:s]
05:308:17:41:07
Timestamp [UCT] (epoch)
2019-01-26 04:58:20 (1548478700)
Block
98936 (1501928 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1367 kB
Tx version
2
RingCT type
0
Extra
01b0e4bc7ac09a4a3fda0e3356ec5ec59692b9709fbfd34e7e3fd750a6dc04f1720321073c180c8d2af3a9b121919742d90ea9811f393f0f358e9f8611bbe8079e2e13dc02140000002bbd0a1e00000000000000000000000000
Outputs
1 output(s) for total of 19.331797030 ARQ
stealth address amount amount idx
00: afb22fb8b3fee7b0fc2f2c940a0bfeb1f2ed448413e4a110b61fb55c39ae8b66 19.331797030 488769 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": 98954, 
  "vin": [ {
      "gen": {
        "height": 98936
      }
    }
  ], 
  "vout": [ {
      "amount": 19331797030, 
      "target": {
        "key": "afb22fb8b3fee7b0fc2f2c940a0bfeb1f2ed448413e4a110b61fb55c39ae8b66"
      }
    }
  ], 
  "extra": [ 1, 176, 228, 188, 122, 192, 154, 74, 63, 218, 14, 51, 86, 236, 94, 197, 150, 146, 185, 112, 159, 191, 211, 78, 126, 63, 215, 80, 166, 220, 4, 241, 114, 3, 33, 7, 60, 24, 12, 141, 42, 243, 169, 177, 33, 145, 151, 66, 217, 14, 169, 129, 31, 57, 63, 15, 53, 142, 159, 134, 17, 187, 232, 7, 158, 46, 19, 220, 2, 20, 0, 0, 0, 43, 189, 10, 30, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}