Transaction Details
Tx hash
866d5a83d2ae0b9a96f7f81751a0499c1111e4b0fd04f32068087bb2b872e0ee
Tx prefix hash
8a7cd112f94e9eda01ed5d0c12fca1f64f39f11b0261cb5b7bef51d712bd3b88
Tx public key
0dc27b524dfd72219a674c21ebd8da4225c7f45b6d21ebcc5d05d4af63b681ad
Age [y:d:h:m:s]
05:064:06:12:46
Timestamp [UCT] (epoch)
2019-09-29 22:14:41 (1569795281)
Block
274940 (1327477 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010dc27b524dfd72219a674c21ebd8da4225c7f45b6d21ebcc5d05d4af63b681ad0321000f537e9df257f9b2c20f710041aa0df932a18666c3c086cfcc6b21af25e32872021b0000000000000000000000000043b0afd300000000000000000000
Outputs
1 output(s) for total of 20.176624830 ARQ
stealth address amount amount idx
00: a07126664176a09f74bb71a6ef220c9c1f3464b66dda6c47619a2275f94d89c0 20.176624830 1234839 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": 274958, 
  "vin": [ {
      "gen": {
        "height": 274940
      }
    }
  ], 
  "vout": [ {
      "amount": 20176624830, 
      "target": {
        "key": "a07126664176a09f74bb71a6ef220c9c1f3464b66dda6c47619a2275f94d89c0"
      }
    }
  ], 
  "extra": [ 1, 13, 194, 123, 82, 77, 253, 114, 33, 154, 103, 76, 33, 235, 216, 218, 66, 37, 199, 244, 91, 109, 33, 235, 204, 93, 5, 212, 175, 99, 182, 129, 173, 3, 33, 0, 15, 83, 126, 157, 242, 87, 249, 178, 194, 15, 113, 0, 65, 170, 13, 249, 50, 161, 134, 102, 195, 192, 134, 207, 204, 107, 33, 175, 37, 227, 40, 114, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 67, 176, 175, 211, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}