Transaction Details
Tx hash
e73ed9ff44755076441c54e7e93fbabff5046053939e422ed6328537a020ba53
Tx prefix hash
d57d640513441c84216de8d811b779f6b7969c2a1ece0ecddd9b94411cbdc469
Tx public key
491f75e9e8e5bc92ccfdf3947c55e638d7b43623b38314b627988a6106b1f682
Age [y:d:h:m:s]
05:155:00:15:12
Timestamp [UCT] (epoch)
2019-07-01 02:15:00 (1561947300)
Block
210210 (1392155 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01491f75e9e8e5bc92ccfdf3947c55e638d7b43623b38314b627988a6106b1f682032100a27dc6ff1e818f129f353e0eadd56204d051971e9966ec4a4029a2329bc9d05f021b000000000000000000000000005060b8f200000000000000000000
Outputs
1 output(s) for total of 18.332776317 ARQ
stealth address amount amount idx
00: c9ea72ca5a83b5fb22ef19fb01b1feba37e3f7126d68f092d81eec57d4dc75de 18.332776317 967634 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": 210228, 
  "vin": [ {
      "gen": {
        "height": 210210
      }
    }
  ], 
  "vout": [ {
      "amount": 18332776317, 
      "target": {
        "key": "c9ea72ca5a83b5fb22ef19fb01b1feba37e3f7126d68f092d81eec57d4dc75de"
      }
    }
  ], 
  "extra": [ 1, 73, 31, 117, 233, 232, 229, 188, 146, 204, 253, 243, 148, 124, 85, 230, 56, 215, 180, 54, 35, 179, 131, 20, 182, 39, 152, 138, 97, 6, 177, 246, 130, 3, 33, 0, 162, 125, 198, 255, 30, 129, 143, 18, 159, 53, 62, 14, 173, 213, 98, 4, 208, 81, 151, 30, 153, 102, 236, 74, 64, 41, 162, 50, 155, 201, 208, 95, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 80, 96, 184, 242, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}