Transaction Details
Tx hash
c38eadd2edf5c248abddd41c0975b9c238abbaa9240271f26c778199dfa22f9b
Tx prefix hash
b34a5a8c4b54aca2f19966e7d7a20a81ee1e4df47daca748502ecc8c8cb38d8a
Tx public key
4d2ace94b5feec1fef47a041313c3e6e1c24fc5335f2e97c8d4f0c2c3c1f6bfb
Age [y:d:h:m:s]
05:160:13:14:39
Timestamp [UCT] (epoch)
2019-06-25 06:43:58 (1561445038)
Block
206027 (1396150 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
014d2ace94b5feec1fef47a041313c3e6e1c24fc5335f2e97c8d4f0c2c3c1f6bfb021100000001091d2b5c00000000000000000003210050cb9a6fb8b4c02a3260719377b77b39ffbc2911fe22194501a19f7ec9aef0df
Outputs
1 output(s) for total of 18.369379554 ARQ
stealth address amount amount idx
00: 9b70c48a1d44b34c7785b2a9e66a7a2bdfe74906457887e48d69333df24d699a 18.369379554 943178 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": 206045, 
  "vin": [ {
      "gen": {
        "height": 206027
      }
    }
  ], 
  "vout": [ {
      "amount": 18369379554, 
      "target": {
        "key": "9b70c48a1d44b34c7785b2a9e66a7a2bdfe74906457887e48d69333df24d699a"
      }
    }
  ], 
  "extra": [ 1, 77, 42, 206, 148, 181, 254, 236, 31, 239, 71, 160, 65, 49, 60, 62, 110, 28, 36, 252, 83, 53, 242, 233, 124, 141, 79, 12, 44, 60, 31, 107, 251, 2, 17, 0, 0, 0, 1, 9, 29, 43, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 80, 203, 154, 111, 184, 180, 192, 42, 50, 96, 113, 147, 119, 183, 123, 57, 255, 188, 41, 17, 254, 34, 25, 69, 1, 161, 159, 126, 201, 174, 240, 223
  ], 
  "rct_signatures": {
    "type": 0
  }
}