Transaction Details
Tx hash
b6d64b7a444d4194153741459855890335f28e66e9c6fc2b2c0118bf9d95572f
Tx prefix hash
89f0705076dfcf3fe9a8ad33a214900f391add704333e0f95807043480b96fc5
Tx public key
333653f39203283fd0833ba0b15f8dc25f2e866d702118073437011c43fef201
Age [y:d:h:m:s]
05:128:12:43:09
Timestamp [UCT] (epoch)
2019-07-27 09:05:19 (1564218319)
Block
229132 (1373105 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01333653f39203283fd0833ba0b15f8dc25f2e866d702118073437011c43fef2010321008abd8d082c259bdc6bd2c2eb020fe5bf0c97d735e19f83611e9e908a8b068c5c021b00000000000000000000000002fc3771c800000000000000000000
Outputs
1 output(s) for total of 18.168174325 ARQ
stealth address amount amount idx
00: d1a2c8374fe1bfa6f1747ea44b0013997fa01c2828ce0c03c92c30be1df074f1 18.168174325 1070233 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": 229150, 
  "vin": [ {
      "gen": {
        "height": 229132
      }
    }
  ], 
  "vout": [ {
      "amount": 18168174325, 
      "target": {
        "key": "d1a2c8374fe1bfa6f1747ea44b0013997fa01c2828ce0c03c92c30be1df074f1"
      }
    }
  ], 
  "extra": [ 1, 51, 54, 83, 243, 146, 3, 40, 63, 208, 131, 59, 160, 177, 95, 141, 194, 95, 46, 134, 109, 112, 33, 24, 7, 52, 55, 1, 28, 67, 254, 242, 1, 3, 33, 0, 138, 189, 141, 8, 44, 37, 155, 220, 107, 210, 194, 235, 2, 15, 229, 191, 12, 151, 215, 53, 225, 159, 131, 97, 30, 158, 144, 138, 139, 6, 140, 92, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 252, 55, 113, 200, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}