Transaction Details
Tx hash
2635faa977faea488e1d0eebce09f5cc2dc9ecb2796b520a260432075794c477
Tx prefix hash
566f975884f01f9e2e3dfed3ab04d306538671596876a5101df44b4725ba9d29
Tx public key
5aa9cc9eb8800e990acb35f66fd82cf610c5d79017a7e1a01198be18e524c923
Age [y:d:h:m:s]
05:310:22:27:47
Timestamp [UCT] (epoch)
2019-01-20 12:20:41 (1547986841)
Block
94912 (1503485 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
015aa9cc9eb8800e990acb35f66fd82cf610c5d79017a7e1a01198be18e524c923032100f487bca20684605fae72a4d2ca69f007a2253c1363e944ef5906f4af6c3a4c75021b0000000000000000000000000032a3caf700000000000000000000
Outputs
1 output(s) for total of 19.369112346 ARQ
stealth address amount amount idx
00: b95e2aeb1c0a4435ee894807714ecc6af01c08809197a8237d88b05655cfc66f 19.369112346 468893 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": 94930, 
  "vin": [ {
      "gen": {
        "height": 94912
      }
    }
  ], 
  "vout": [ {
      "amount": 19369112346, 
      "target": {
        "key": "b95e2aeb1c0a4435ee894807714ecc6af01c08809197a8237d88b05655cfc66f"
      }
    }
  ], 
  "extra": [ 1, 90, 169, 204, 158, 184, 128, 14, 153, 10, 203, 53, 246, 111, 216, 44, 246, 16, 197, 215, 144, 23, 167, 225, 160, 17, 152, 190, 24, 229, 36, 201, 35, 3, 33, 0, 244, 135, 188, 162, 6, 132, 96, 95, 174, 114, 164, 210, 202, 105, 240, 7, 162, 37, 60, 19, 99, 233, 68, 239, 89, 6, 244, 175, 108, 58, 76, 117, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 50, 163, 202, 247, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}