Transaction Details
Tx hash
1e15a12156f91eea64e4b49c964d820a9a150b616b8f3070d023391877784c3b
Tx prefix hash
b617b38add3e6e5b9c2541d706ebed884b44b7bb9f118a4229cf8aa9933d85c2
Tx public key
85b9f1a4d3f1613d230cbe0d9ef3c917d5cf1dfb8876edfd803627add546c0e8
Age [y:d:h:m:s]
05:111:18:26:41
Timestamp [UCT] (epoch)
2019-08-10 21:21:46 (1565472106)
Block
239537 (1361146 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0185b9f1a4d3f1613d230cbe0d9ef3c917d5cf1dfb8876edfd803627add546c0e80211000000b427ccf6db000000000000000000032100e482e41e9e4a31f08f8da024271757cda72bfc74554f63154d16fc38c41e5d64
Outputs
1 output(s) for total of 18.078191219 ARQ
stealth address amount amount idx
00: 8bbc02e1c5adcfa4d7aef9897d896b4029e6f525936b44ce81ae483adc2da80f 18.078191219 1095129 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": 239555, 
  "vin": [ {
      "gen": {
        "height": 239537
      }
    }
  ], 
  "vout": [ {
      "amount": 18078191219, 
      "target": {
        "key": "8bbc02e1c5adcfa4d7aef9897d896b4029e6f525936b44ce81ae483adc2da80f"
      }
    }
  ], 
  "extra": [ 1, 133, 185, 241, 164, 211, 241, 97, 61, 35, 12, 190, 13, 158, 243, 201, 23, 213, 207, 29, 251, 136, 118, 237, 253, 128, 54, 39, 173, 213, 70, 192, 232, 2, 17, 0, 0, 0, 180, 39, 204, 246, 219, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 228, 130, 228, 30, 158, 74, 49, 240, 143, 141, 160, 36, 39, 23, 87, 205, 167, 43, 252, 116, 85, 79, 99, 21, 77, 22, 252, 56, 196, 30, 93, 100
  ], 
  "rct_signatures": {
    "type": 0
  }
}