Transaction Details
Tx hash
893beb8f5bd88003aac1259dbfca1532bfb66c31c104ae160b7b83343b520e59
Tx prefix hash
c81b806461167306c0e9e3416a502846c00f0743f262e7f2e7268344b667735a
Tx public key
0caf4ed9846a2343a620d18dd8dfed149637b8c1e9ea65fbe10105144aa13884
Age [y:d:h:m:s]
05:310:19:45:16
Timestamp [UCT] (epoch)
2019-01-23 21:36:11 (1548279371)
Block
97325 (1503394 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010caf4ed9846a2343a620d18dd8dfed149637b8c1e9ea65fbe10105144aa13884032100e333e7e9b19fdbd026979b99d6d2d9a3107cee806518299ecfa1369821206781021b00000000000000000000000000281cc7cc00000000000000000000
Outputs
1 output(s) for total of 19.346629891 ARQ
stealth address amount amount idx
00: d20d1052a0d1f33875b070d843827941b62e4dc19c533f52f3d3f8561e93bd13 19.346629891 480238 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": 97343, 
  "vin": [ {
      "gen": {
        "height": 97325
      }
    }
  ], 
  "vout": [ {
      "amount": 19346629891, 
      "target": {
        "key": "d20d1052a0d1f33875b070d843827941b62e4dc19c533f52f3d3f8561e93bd13"
      }
    }
  ], 
  "extra": [ 1, 12, 175, 78, 217, 132, 106, 35, 67, 166, 32, 209, 141, 216, 223, 237, 20, 150, 55, 184, 193, 233, 234, 101, 251, 225, 1, 5, 20, 74, 161, 56, 132, 3, 33, 0, 227, 51, 231, 233, 177, 159, 219, 208, 38, 151, 155, 153, 214, 210, 217, 163, 16, 124, 238, 128, 101, 24, 41, 158, 207, 161, 54, 152, 33, 32, 103, 129, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 40, 28, 199, 204, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}