Transaction Details
Tx hash
444fdea417ba89226327eed6a98aca0411bd79599465b65f3ad6b62f708d9eac
Tx prefix hash
537c6d627a978ed05fb82c449beb4dceb1f9c446f2491236fcc15af0564800b1
Tx public key
1a827ac917e99b7612e766e186672630f54e1d58d03cc99e2190b03b7c117034
Age [y:d:h:m:s]
05:173:08:49:39
Timestamp [UCT] (epoch)
2019-06-10 01:01:49 (1560128509)
Block
195186 (1405304 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
011a827ac917e99b7612e766e186672630f54e1d58d03cc99e2190b03b7c117034021100000002d99288b8000000000000000000032100ab5611e6e7f9886e4d444445d5e16a986363ad1558e0ff63c322e57d1fb3f89b
Outputs
1 output(s) for total of 18.464716976 ARQ
stealth address amount amount idx
00: 331fcabb9664bfdbee71b44347ec38372d6e926972da42e954d08d5a05aa97b6 18.464716976 882043 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": 195204, 
  "vin": [ {
      "gen": {
        "height": 195186
      }
    }
  ], 
  "vout": [ {
      "amount": 18464716976, 
      "target": {
        "key": "331fcabb9664bfdbee71b44347ec38372d6e926972da42e954d08d5a05aa97b6"
      }
    }
  ], 
  "extra": [ 1, 26, 130, 122, 201, 23, 233, 155, 118, 18, 231, 102, 225, 134, 103, 38, 48, 245, 78, 29, 88, 208, 60, 201, 158, 33, 144, 176, 59, 124, 17, 112, 52, 2, 17, 0, 0, 0, 2, 217, 146, 136, 184, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 171, 86, 17, 230, 231, 249, 136, 110, 77, 68, 68, 69, 213, 225, 106, 152, 99, 99, 173, 21, 88, 224, 255, 99, 195, 34, 229, 125, 31, 179, 248, 155
  ], 
  "rct_signatures": {
    "type": 0
  }
}