Transaction Details
Tx hash
bfc8cfb6e8df57cab0ec27df4de3c6d5f9cf32c40dbe9888f1c0dcc2c108e682
Tx prefix hash
4f41a7acc8eb89f9f307033475f7c79e839b55ba323aa84d198ef52a5eaebb75
Tx public key
cc853fcbea5673f14b5e7ff77b4cb084faf2cd0946a8ba5ac3423bd90da670d6
Age [y:d:h:m:s]
05:173:16:53:52
Timestamp [UCT] (epoch)
2019-06-10 02:12:35 (1560132755)
Block
195218 (1405547 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01cc853fcbea5673f14b5e7ff77b4cb084faf2cd0946a8ba5ac3423bd90da670d6032100a25c4359dfd4771f6a0b60e3f4bae751a6873f45000e3b9a99d8702b0aec7522021b000000000000000000000000000f4d028e00000000000000000000
Outputs
1 output(s) for total of 18.464302211 ARQ
stealth address amount amount idx
00: d9f6926508a5e47b903262748f3a41d5572f7ffa963e4df7a065b36f4c4792dd 18.464302211 882174 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": 195236, 
  "vin": [ {
      "gen": {
        "height": 195218
      }
    }
  ], 
  "vout": [ {
      "amount": 18464302211, 
      "target": {
        "key": "d9f6926508a5e47b903262748f3a41d5572f7ffa963e4df7a065b36f4c4792dd"
      }
    }
  ], 
  "extra": [ 1, 204, 133, 63, 203, 234, 86, 115, 241, 75, 94, 127, 247, 123, 76, 176, 132, 250, 242, 205, 9, 70, 168, 186, 90, 195, 66, 59, 217, 13, 166, 112, 214, 3, 33, 0, 162, 92, 67, 89, 223, 212, 119, 31, 106, 11, 96, 227, 244, 186, 231, 81, 166, 135, 63, 69, 0, 14, 59, 154, 153, 216, 112, 43, 10, 236, 117, 34, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 15, 77, 2, 142, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}