Transaction Details
Tx hash
5ca95c0d373b1a91be1ac2dd545aa8a4700e926e510eb0d3f8cdee759d982eba
Tx prefix hash
1f780aff98a22258a7f944802efd0c66df961a2f463c4616f29563f31d9cc151
Tx public key
0d3b9b62afe160e3fc8b4d0f53a0b28957083ae74f0fee03a979501dbdb8c1aa
Age [y:d:h:m:s]
05:127:11:31:57
Timestamp [UCT] (epoch)
2019-07-26 09:13:31 (1564132411)
Block
228412 (1372394 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010d3b9b62afe160e3fc8b4d0f53a0b28957083ae74f0fee03a979501dbdb8c1aa03210050b02b2a065c62b5696381397d00ba2676ba2047d8f1d27c3c7c56629b6a94e0021b00000000000000000000000004e6c0af7800000000000000000000
Outputs
1 output(s) for total of 18.174347492 ARQ
stealth address amount amount idx
00: 63eb766e4e66f96a80d8f66d754b0a80ac21eee361ba6cfd5c562afb0fd64f0e 18.174347492 1068138 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": 228430, 
  "vin": [ {
      "gen": {
        "height": 228412
      }
    }
  ], 
  "vout": [ {
      "amount": 18174347492, 
      "target": {
        "key": "63eb766e4e66f96a80d8f66d754b0a80ac21eee361ba6cfd5c562afb0fd64f0e"
      }
    }
  ], 
  "extra": [ 1, 13, 59, 155, 98, 175, 225, 96, 227, 252, 139, 77, 15, 83, 160, 178, 137, 87, 8, 58, 231, 79, 15, 238, 3, 169, 121, 80, 29, 189, 184, 193, 170, 3, 33, 0, 80, 176, 43, 42, 6, 92, 98, 181, 105, 99, 129, 57, 125, 0, 186, 38, 118, 186, 32, 71, 216, 241, 210, 124, 60, 124, 86, 98, 155, 106, 148, 224, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 230, 192, 175, 120, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}