Transaction Details
Tx hash
b117b3d9bb9e82830c75aa2dec1b09d85a1cebb1868b3f433edc8265c82b4555
Tx prefix hash
bc5cd9062d7288c13e860839ed378832fdd5aa2ef1efab3ee5dd4b427d39a05a
Tx public key
f445cfde962e5d1e5ae3a399bf6758606f638a5f7e9a1a5a457053f7808a7cfd
Age [y:d:h:m:s]
05:212:03:45:42
Timestamp [UCT] (epoch)
2019-05-02 04:38:46 (1556771926)
Block
167428 (1433029 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f445cfde962e5d1e5ae3a399bf6758606f638a5f7e9a1a5a457053f7808a7cfd032100fa244c43a40bb8a4a557c2b943c1148d08a3b20930bfffe3c0199c2f8dbd5b97021b00000000000000000000000000e001d3b100000000000000000000
Outputs
1 output(s) for total of 18.710606687 ARQ
stealth address amount amount idx
00: a5b375d38425d4f1dd289a28cbe699541c2d3aa287441973eef6fe21c816b1c7 18.710606687 761986 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": 167446, 
  "vin": [ {
      "gen": {
        "height": 167428
      }
    }
  ], 
  "vout": [ {
      "amount": 18710606687, 
      "target": {
        "key": "a5b375d38425d4f1dd289a28cbe699541c2d3aa287441973eef6fe21c816b1c7"
      }
    }
  ], 
  "extra": [ 1, 244, 69, 207, 222, 150, 46, 93, 30, 90, 227, 163, 153, 191, 103, 88, 96, 111, 99, 138, 95, 126, 154, 26, 90, 69, 112, 83, 247, 128, 138, 124, 253, 3, 33, 0, 250, 36, 76, 67, 164, 11, 184, 164, 165, 87, 194, 185, 67, 193, 20, 141, 8, 163, 178, 9, 48, 191, 255, 227, 192, 25, 156, 47, 141, 189, 91, 151, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 224, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}