Transaction Details
Tx hash
508edfbdaea3afb90e1b8583e39bb101e9eb89293b8af98de23569c6db642e40
Tx prefix hash
48847eebd2a6760a8eef8bb1dca1f6c28611e052c87be1d8b877e057c628a831
Tx public key
2e237e200c82a7fd0ba520d8cd9d60dfee1d8d08dacc3e9b878d52835c1b8cec
Age [y:d:h:m:s]
05:110:13:50:54
Timestamp [UCT] (epoch)
2019-08-09 17:39:34 (1565372374)
Block
238720 (1360292 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
012e237e200c82a7fd0ba520d8cd9d60dfee1d8d08dacc3e9b878d52835c1b8cec0321005a392d9bf6938845a7fc77b2bd36ba580a5880c3b03de43930ac4a2dd949c9f0021b0000000000000000000000000ad7fd0e1700000000000000000000
Outputs
1 output(s) for total of 18.085235421 ARQ
stealth address amount amount idx
00: ed7ee7297888b67b4beaf2d01d91d021c7f87f04d733436fc64aa1efebafc7c0 18.085235421 1093618 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": 238738, 
  "vin": [ {
      "gen": {
        "height": 238720
      }
    }
  ], 
  "vout": [ {
      "amount": 18085235421, 
      "target": {
        "key": "ed7ee7297888b67b4beaf2d01d91d021c7f87f04d733436fc64aa1efebafc7c0"
      }
    }
  ], 
  "extra": [ 1, 46, 35, 126, 32, 12, 130, 167, 253, 11, 165, 32, 216, 205, 157, 96, 223, 238, 29, 141, 8, 218, 204, 62, 155, 135, 141, 82, 131, 92, 27, 140, 236, 3, 33, 0, 90, 57, 45, 155, 246, 147, 136, 69, 167, 252, 119, 178, 189, 54, 186, 88, 10, 88, 128, 195, 176, 61, 228, 57, 48, 172, 74, 45, 217, 73, 201, 240, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 215, 253, 14, 23, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}