Transaction Details
Tx hash
572df0abafff9eeaba3e41bf232d95906b401c108b16941a98c6d37d8c00268c
Tx prefix hash
e27162d74e0a60c7b9063a2a57f48f8ef012802902dc02ac4c10807d423a4f03
Tx public key
e59a6734f2fc6c9f23217ce9075001c96eab92c858b60adfde57e0471440a33d
Age [y:d:h:m:s]
05:348:19:46:43
Timestamp [UCT] (epoch)
2018-12-14 01:55:44 (1544752544)
Block
68317 (1530404 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01e59a6734f2fc6c9f23217ce9075001c96eab92c858b60adfde57e0471440a33d0321001a0466b5a6bc45f24523124ace5633cc0d8175c9a1148656a48a18207d1e9b5e02100000009a170801000000000000000000
Outputs
1 output(s) for total of 19.616093653 ARQ
stealth address amount amount idx
00: 141eea6e0682841ffd543099842fa09ddf537a08e2d99382fbddc814ec710b9e 19.616093653 359433 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": 68335, 
  "vin": [ {
      "gen": {
        "height": 68317
      }
    }
  ], 
  "vout": [ {
      "amount": 19616093653, 
      "target": {
        "key": "141eea6e0682841ffd543099842fa09ddf537a08e2d99382fbddc814ec710b9e"
      }
    }
  ], 
  "extra": [ 1, 229, 154, 103, 52, 242, 252, 108, 159, 35, 33, 124, 233, 7, 80, 1, 201, 110, 171, 146, 200, 88, 182, 10, 223, 222, 87, 224, 71, 20, 64, 163, 61, 3, 33, 0, 26, 4, 102, 181, 166, 188, 69, 242, 69, 35, 18, 74, 206, 86, 51, 204, 13, 129, 117, 201, 161, 20, 134, 86, 164, 138, 24, 32, 125, 30, 155, 94, 2, 16, 0, 0, 0, 154, 23, 8, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}