Transaction Details
Tx hash
ce365a7d7b049c68b6ed0634287ba3e23ae1798260b8adb3b3d049add8e4dcd1
Tx prefix hash
3753078493bfbf0eba6348df2cf4f26206c07d9ec98ee284805e26c959a4f603
Tx public key
71410dc1a89a7d181cdc237c31bd185bf8d4930972f0e78237b3c1c7b6c8b9e2
Age [y:d:h:m:s]
05:101:06:22:08
Timestamp [UCT] (epoch)
2019-08-20 22:20:20 (1566339620)
Block
246770 (1353578 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0171410dc1a89a7d181cdc237c31bd185bf8d4930972f0e78237b3c1c7b6c8b9e2032100c05db235be85193e23c3aad13b2ce6ef8feca3251afff9ef26e29b9b32d09c2e021b0000000000000000000000001639fd0e1700000000000000000000
Outputs
1 output(s) for total of 18.015947588 ARQ
stealth address amount amount idx
00: 7d0667afc4943dd8fb92ab92d66e7af2517205f1c76fcabb29e27cb0658e3547 18.015947588 1108037 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": 246788, 
  "vin": [ {
      "gen": {
        "height": 246770
      }
    }
  ], 
  "vout": [ {
      "amount": 18015947588, 
      "target": {
        "key": "7d0667afc4943dd8fb92ab92d66e7af2517205f1c76fcabb29e27cb0658e3547"
      }
    }
  ], 
  "extra": [ 1, 113, 65, 13, 193, 168, 154, 125, 24, 28, 220, 35, 124, 49, 189, 24, 91, 248, 212, 147, 9, 114, 240, 231, 130, 55, 179, 193, 199, 182, 200, 185, 226, 3, 33, 0, 192, 93, 178, 53, 190, 133, 25, 62, 35, 195, 170, 209, 59, 44, 230, 239, 143, 236, 163, 37, 26, 255, 249, 239, 38, 226, 155, 155, 50, 208, 156, 46, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 22, 57, 253, 14, 23, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}