Transaction Details
Tx hash
5e559396d255af15275001f5895a00ee094bc621892ef20abf45a2c1d24fb3a0
Tx prefix hash
ef7e20c401a88bdd068a03d99bdc5e47e9149f44ec4d372f620ae826a261f28e
Tx public key
3816d172494af8e56f4d86230ef638ff100af889afb20430c1f484352be5b89f
Age [y:d:h:m:s]
05:360:02:13:03
Timestamp [UCT] (epoch)
2018-12-05 06:23:24 (1543991004)
Block
61989 (1538471 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
013816d172494af8e56f4d86230ef638ff100af889afb20430c1f484352be5b89f03210043ae9d8d0f7ae5d17153578920618856ad6e24af3b38db63edf48a8cfa0fa76c02100000009f8a5f0e000000000000000000
Outputs
1 output(s) for total of 19.675373160 ARQ
stealth address amount amount idx
00: 37e16fdb7add26fb4a091d24d8c84d834d53491ede329abac4b4bcfa771d43b6 19.675373160 335702 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": 62007, 
  "vin": [ {
      "gen": {
        "height": 61989
      }
    }
  ], 
  "vout": [ {
      "amount": 19675373160, 
      "target": {
        "key": "37e16fdb7add26fb4a091d24d8c84d834d53491ede329abac4b4bcfa771d43b6"
      }
    }
  ], 
  "extra": [ 1, 56, 22, 209, 114, 73, 74, 248, 229, 111, 77, 134, 35, 14, 246, 56, 255, 16, 10, 248, 137, 175, 178, 4, 48, 193, 244, 132, 53, 43, 229, 184, 159, 3, 33, 0, 67, 174, 157, 141, 15, 122, 229, 209, 113, 83, 87, 137, 32, 97, 136, 86, 173, 110, 36, 175, 59, 56, 219, 99, 237, 244, 138, 140, 250, 15, 167, 108, 2, 16, 0, 0, 0, 159, 138, 95, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}