Transaction Details
Tx hash
680ae74bea65767e7b46c95cc9b3fdac7ac95e5535b21a9994fe639a68750f6e
Tx prefix hash
bb4edbc2a4932f03de07bc8c03f86e4bcfedc1120ae24cb2abf3c8df4b774259
Tx public key
784f960efeca8c65dc031d602aaeba1f462da7f4b5dfb8a27d0eeace9819f6e2
Age [y:d:h:m:s]
05:068:09:16:33
Timestamp [UCT] (epoch)
2019-08-01 23:01:55 (1564700515)
Block
233153 (1330615 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01784f960efeca8c65dc031d602aaeba1f462da7f4b5dfb8a27d0eeace9819f6e20321006f0df38b9b890305780ec153a2a1bc452741cde620de9e0da5ca2dd5dc32bc17021b0000000000000000000000000a037975fa00000000000000000000
Outputs
1 output(s) for total of 18.133307415 ARQ
stealth address amount amount idx
00: 061984369d10134ccf9aed851f3f3ab7c4ac1ba703b9adabd2d7db1a22807aa0 18.133307415 1081603 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": 233171, 
  "vin": [ {
      "gen": {
        "height": 233153
      }
    }
  ], 
  "vout": [ {
      "amount": 18133307415, 
      "target": {
        "key": "061984369d10134ccf9aed851f3f3ab7c4ac1ba703b9adabd2d7db1a22807aa0"
      }
    }
  ], 
  "extra": [ 1, 120, 79, 150, 14, 254, 202, 140, 101, 220, 3, 29, 96, 42, 174, 186, 31, 70, 45, 167, 244, 181, 223, 184, 162, 125, 14, 234, 206, 152, 25, 246, 226, 3, 33, 0, 111, 13, 243, 139, 155, 137, 3, 5, 120, 14, 193, 83, 162, 161, 188, 69, 39, 65, 205, 230, 32, 222, 158, 13, 165, 202, 45, 213, 220, 50, 188, 23, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 3, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}