Transaction Details
Tx hash
6a188fdd4417c0185022c32dce8e5df9ba7c1e492ed64f66195cee0394eed6ec
Tx prefix hash
15335986136727a556240ef1234451460e1a2dace1f8fc28f4c89bf37de7e119
Tx public key
544a1439c7308d3bb63c8a74ff5a2c8ddaf8e423d736452b36ececbb3dfb0be8
Age [y:d:h:m:s]
05:233:13:05:29
Timestamp [UCT] (epoch)
2019-04-07 09:50:23 (1554630623)
Block
149709 (1448339 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01544a1439c7308d3bb63c8a74ff5a2c8ddaf8e423d736452b36ececbb3dfb0be8032100376fc73515e575a3bd8cacacbd851f7a842140572b7cf46457086e0ddfc71e3f021b000000000000000000000000001750544100000000000000000000
Outputs
1 output(s) for total of 18.869363824 ARQ
stealth address amount amount idx
00: 95523143c821d9ff3fdcf2e595f5237ca089452bf37b47d94a6bc39b76975b0c 18.869363824 685363 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": 149727, 
  "vin": [ {
      "gen": {
        "height": 149709
      }
    }
  ], 
  "vout": [ {
      "amount": 18869363824, 
      "target": {
        "key": "95523143c821d9ff3fdcf2e595f5237ca089452bf37b47d94a6bc39b76975b0c"
      }
    }
  ], 
  "extra": [ 1, 84, 74, 20, 57, 199, 48, 141, 59, 182, 60, 138, 116, 255, 90, 44, 141, 218, 248, 228, 35, 215, 54, 69, 43, 54, 236, 236, 187, 61, 251, 11, 232, 3, 33, 0, 55, 111, 199, 53, 21, 229, 117, 163, 189, 140, 172, 172, 189, 133, 31, 122, 132, 33, 64, 87, 43, 124, 244, 100, 87, 8, 110, 13, 223, 199, 30, 63, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 23, 80, 84, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}