Transaction Details
Tx hash
ec6c29d771456e7d5c4bdc59d0dc22da6fb7f9d9a32f2f350461366531980fe0
Tx prefix hash
d97fc431571955bdee8ed2e8c7736c4f6f0c33c065fb02a09b02ae5cc8a7bb68
Tx public key
c727b48e883f53c0aeb176dcf26c7e94ea9a1e69a1b787610a4292414d3dbe0f
Age [y:d:h:m:s]
05:116:19:54:26
Timestamp [UCT] (epoch)
2019-08-06 13:48:01 (1565099281)
Block
236469 (1364712 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c727b48e883f53c0aeb176dcf26c7e94ea9a1e69a1b787610a4292414d3dbe0f0321009d5a8c66d3383167e1b74b6c83d26b5b2bf30a3de5685e80114370d9e44d57db021b000000000000000000000000043b76922e00000000000000000000
Outputs
1 output(s) for total of 18.104657824 ARQ
stealth address amount amount idx
00: 51d01d4e7f78a4e02d2da2529e306f401e3a1b98e24f73c92bee7ab055e4df2c 18.104657824 1089505 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": 236487, 
  "vin": [ {
      "gen": {
        "height": 236469
      }
    }
  ], 
  "vout": [ {
      "amount": 18104657824, 
      "target": {
        "key": "51d01d4e7f78a4e02d2da2529e306f401e3a1b98e24f73c92bee7ab055e4df2c"
      }
    }
  ], 
  "extra": [ 1, 199, 39, 180, 142, 136, 63, 83, 192, 174, 177, 118, 220, 242, 108, 126, 148, 234, 154, 30, 105, 161, 183, 135, 97, 10, 66, 146, 65, 77, 61, 190, 15, 3, 33, 0, 157, 90, 140, 102, 211, 56, 49, 103, 225, 183, 75, 108, 131, 210, 107, 91, 43, 243, 10, 61, 229, 104, 94, 128, 17, 67, 112, 217, 228, 77, 87, 219, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 59, 118, 146, 46, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}