Transaction Details
Tx hash
b6aff75d43493b2c3e8221ce3c80ba1207f70ef0b7d7f64defddbc782c34b2c0
Tx prefix hash
91e9a49b6b954dced0ecafc4dfadc4eaa3485285da977f1f58c808a40f7dbe2c
Tx public key
eea53ecc2fee43f96cf8e3d3b431bfd495a8714a65c287a4f088be73b6f2a230
Age [y:d:h:m:s]
05:221:13:07:35
Timestamp [UCT] (epoch)
2019-07-03 16:11:40 (1562170300)
Block
212048 (1434660 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01eea53ecc2fee43f96cf8e3d3b431bfd495a8714a65c287a4f088be73b6f2a23002110000013d091d2b5c000000000000000000032100abc26fbe438b35d413188d2f5a7536e72930dc7247e6e3d7170f9155b3aaebf1
Outputs
1 output(s) for total of 18.316716018 ARQ
stealth address amount amount idx
00: 6702b0450cd0f3cd4ae3faf1cd617b3c3b41b0b82e94c9f15040fc91f563f082 18.316716018 978984 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": 212066, 
  "vin": [ {
      "gen": {
        "height": 212048
      }
    }
  ], 
  "vout": [ {
      "amount": 18316716018, 
      "target": {
        "key": "6702b0450cd0f3cd4ae3faf1cd617b3c3b41b0b82e94c9f15040fc91f563f082"
      }
    }
  ], 
  "extra": [ 1, 238, 165, 62, 204, 47, 238, 67, 249, 108, 248, 227, 211, 180, 49, 191, 212, 149, 168, 113, 74, 101, 194, 135, 164, 240, 136, 190, 115, 182, 242, 162, 48, 2, 17, 0, 0, 1, 61, 9, 29, 43, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 171, 194, 111, 190, 67, 139, 53, 212, 19, 24, 141, 47, 90, 117, 54, 231, 41, 48, 220, 114, 71, 230, 227, 215, 23, 15, 145, 85, 179, 170, 235, 241
  ], 
  "rct_signatures": {
    "type": 0
  }
}