Transaction Details
Tx hash
ae37ef86f2e8b74e18191f896b786db3fb244bcc3f9f6af662ffd036586880ec
Tx prefix hash
b11a58e00055d6e67e5f24a0efb3f3e9a0072e3aad4d0b0e79e3c44dfbfdbb58
Tx public key
9ef6009b197f25a8942bc0a65c9de4b415d413b7d2b813a451ef533fa1f6c906
Age [y:d:h:m:s]
05:350:05:32:20
Timestamp [UCT] (epoch)
2018-12-15 14:58:07 (1544885887)
Block
69346 (1531453 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019ef6009b197f25a8942bc0a65c9de4b415d413b7d2b813a451ef533fa1f6c90603210091151b48b13bfd117b07bbb305beeef6d5eab3beaa7e557b458194fe5f562958021b0000000000000000000000000021e1a99f00000000000000000000
Outputs
1 output(s) for total of 19.607355172 ARQ
stealth address amount amount idx
00: fa14df4ad0b136bfe7dde41b1282c686d98ede3c72995f3a4131a2de37253c8c 19.607355172 363229 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": 69364, 
  "vin": [ {
      "gen": {
        "height": 69346
      }
    }
  ], 
  "vout": [ {
      "amount": 19607355172, 
      "target": {
        "key": "fa14df4ad0b136bfe7dde41b1282c686d98ede3c72995f3a4131a2de37253c8c"
      }
    }
  ], 
  "extra": [ 1, 158, 246, 0, 155, 25, 127, 37, 168, 148, 43, 192, 166, 92, 157, 228, 180, 21, 212, 19, 183, 210, 184, 19, 164, 81, 239, 83, 63, 161, 246, 201, 6, 3, 33, 0, 145, 21, 27, 72, 177, 59, 253, 17, 123, 7, 187, 179, 5, 190, 238, 246, 213, 234, 179, 190, 170, 126, 85, 123, 69, 129, 148, 254, 95, 86, 41, 88, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 33, 225, 169, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}