Transaction Details
Tx hash
52ed852bb35e087397bf4491c48146cae270b40f988b92a028afb2c9bb895594
Tx prefix hash
c0d0045c0d931f501d3c5542fec7d91bc1b711e7a0e671ff458a64574fa142da
Tx public key
0a89fa1f11461ca58cb0b9717fd0deb8e57190a161f3a4174eebecad8b38ee68
Age [y:d:h:m:s]
05:278:19:11:05
Timestamp [UCT] (epoch)
2019-02-21 14:19:22 (1550758762)
Block
117804 (1480566 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010a89fa1f11461ca58cb0b9717fd0deb8e57190a161f3a4174eebecad8b38ee680321006a2b4c11ee0eaceba444beb640e41d24eca72973e797710922eeace9acca0235021b000000000000000000000000003de59e0d00000000000000000000
Outputs
1 output(s) for total of 19.158627176 ARQ
stealth address amount amount idx
00: fd0e9e636cd8ce4f74536e8607b90c2f86ac49aa4fdc8f355256e4d220d274bd 19.158627176 572256 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": 117822, 
  "vin": [ {
      "gen": {
        "height": 117804
      }
    }
  ], 
  "vout": [ {
      "amount": 19158627176, 
      "target": {
        "key": "fd0e9e636cd8ce4f74536e8607b90c2f86ac49aa4fdc8f355256e4d220d274bd"
      }
    }
  ], 
  "extra": [ 1, 10, 137, 250, 31, 17, 70, 28, 165, 140, 176, 185, 113, 127, 208, 222, 184, 229, 113, 144, 161, 97, 243, 164, 23, 78, 235, 236, 173, 139, 56, 238, 104, 3, 33, 0, 106, 43, 76, 17, 238, 14, 172, 235, 164, 68, 190, 182, 64, 228, 29, 36, 236, 167, 41, 115, 231, 151, 113, 9, 34, 238, 172, 233, 172, 202, 2, 53, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 61, 229, 158, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}