Transaction Details
Tx hash
66ca09820ab92398a3ee83a96159c934ea44f36d7ed24fb8ac4a71807bc2c909
Tx prefix hash
c36ce7c4a6bc947b9f700ec12c12731eee3954f079d77a82f2754333e6ce0ec8
Tx public key
804a0685664498280c6b9816036872699e22f9e55702e96a9b302516868d5f70
Age [y:d:h:m:s]
05:296:20:47:35
Timestamp [UCT] (epoch)
2019-02-05 13:48:37 (1549374517)
Block
106360 (1493443 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01804a0685664498280c6b9816036872699e22f9e55702e96a9b302516868d5f700321002556241a6693ed8d8b684dabb0b78bcf446127edb1e9df3708f0d944438b9b3a021b0000000000000000000000000003d45c1400000000000000000000
Outputs
1 output(s) for total of 19.263459656 ARQ
stealth address amount amount idx
00: 515a64a9f6cb6012f5e3f87a78bd6c5e6a224e821978a2aaaa895cf5021cddf0 19.263459656 523584 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": 106378, 
  "vin": [ {
      "gen": {
        "height": 106360
      }
    }
  ], 
  "vout": [ {
      "amount": 19263459656, 
      "target": {
        "key": "515a64a9f6cb6012f5e3f87a78bd6c5e6a224e821978a2aaaa895cf5021cddf0"
      }
    }
  ], 
  "extra": [ 1, 128, 74, 6, 133, 102, 68, 152, 40, 12, 107, 152, 22, 3, 104, 114, 105, 158, 34, 249, 229, 87, 2, 233, 106, 155, 48, 37, 22, 134, 141, 95, 112, 3, 33, 0, 37, 86, 36, 26, 102, 147, 237, 141, 139, 104, 77, 171, 176, 183, 139, 207, 68, 97, 39, 237, 177, 233, 223, 55, 8, 240, 217, 68, 67, 139, 155, 58, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 212, 92, 20, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}