Transaction Details
Tx hash
b65e695d058c3b9aa24902e74c849fce9323d2a2ac506f5acf7d7538ef8eb121
Tx prefix hash
f1e82d575cd8e3cbb75dc86a0b29f8a66774a9bc27bf0dc8b875f842019d65fd
Tx public key
d455c57bd61ca8b6d23c65a1a0d5b9a8d3c30b5941ec7fe17f10ffffacc75e08
Age [y:d:h:m:s]
05:057:08:46:56
Timestamp [UCT] (epoch)
2019-08-07 07:02:12 (1565161332)
Block
237007 (1322773 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d455c57bd61ca8b6d23c65a1a0d5b9a8d3c30b5941ec7fe17f10ffffacc75e08032100f8a59935498525b8a0c0e3e4e373942e331a08abd3e380df3963828e77fbd74f021b000000000000000000000000056b1522be00000000000000000000
Outputs
1 output(s) for total of 18.100013879 ARQ
stealth address amount amount idx
00: 19ccf37697c87cedaa11c95b87a5691ee5137ab0818d8a2f80f2e42000e3a89e 18.100013879 1090430 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": 237025, 
  "vin": [ {
      "gen": {
        "height": 237007
      }
    }
  ], 
  "vout": [ {
      "amount": 18100013879, 
      "target": {
        "key": "19ccf37697c87cedaa11c95b87a5691ee5137ab0818d8a2f80f2e42000e3a89e"
      }
    }
  ], 
  "extra": [ 1, 212, 85, 197, 123, 214, 28, 168, 182, 210, 60, 101, 161, 160, 213, 185, 168, 211, 195, 11, 89, 65, 236, 127, 225, 127, 16, 255, 255, 172, 199, 94, 8, 3, 33, 0, 248, 165, 153, 53, 73, 133, 37, 184, 160, 192, 227, 228, 227, 115, 148, 46, 51, 26, 8, 171, 211, 227, 128, 223, 57, 99, 130, 142, 119, 251, 215, 79, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 107, 21, 34, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}