Transaction Details
Tx hash
d3df574316ea8ef85ec08f151050b5ed75ac5a609c2ec7d81857b6640ba7f83d
Tx prefix hash
5fb3ea816f897495b33d5f1af39fa4a97329f5afb9d0c71b4c4b74dd6f074764
Tx public key
7fa1f5f29487e04b7a189b8de5c8aa5b1f0ab61319acef97ae3277c7252cb94e
Age [y:d:h:m:s]
05:169:11:44:15
Timestamp [UCT] (epoch)
2019-06-11 01:34:13 (1560216853)
Block
195919 (1402555 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
017fa1f5f29487e04b7a189b8de5c8aa5b1f0ab61319acef97ae3277c7252cb94e0321000e036392350e84b01a218360a4a46ffc81d9ca92555e77c5e017483c1d93cd09021b00000000000000000000000000fbb5633400000000000000000000
Outputs
1 output(s) for total of 18.458131311 ARQ
stealth address amount amount idx
00: 7b077344a9ae093a992e5939ab7648346eb56aa43d89f1d3f2ddc64b6e4be319 18.458131311 885453 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": 195937, 
  "vin": [ {
      "gen": {
        "height": 195919
      }
    }
  ], 
  "vout": [ {
      "amount": 18458131311, 
      "target": {
        "key": "7b077344a9ae093a992e5939ab7648346eb56aa43d89f1d3f2ddc64b6e4be319"
      }
    }
  ], 
  "extra": [ 1, 127, 161, 245, 242, 148, 135, 224, 75, 122, 24, 155, 141, 229, 200, 170, 91, 31, 10, 182, 19, 25, 172, 239, 151, 174, 50, 119, 199, 37, 44, 185, 78, 3, 33, 0, 14, 3, 99, 146, 53, 14, 132, 176, 26, 33, 131, 96, 164, 164, 111, 252, 129, 217, 202, 146, 85, 94, 119, 197, 224, 23, 72, 60, 29, 147, 205, 9, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 251, 181, 99, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}