Transaction Details
Tx hash
27e184707e003045e6e608cf86a7e543359e74a5f3a5577d3074098d25600b5a
Tx prefix hash
d2c8c9af674a3089ac99f48e67d4829235bf9170851b7b601bf47b215f30ec36
Tx public key
f2d709c69fea71894c910f3c559e668127e25ef58ca6ec515fd94a280a88a250
Age [y:d:h:m:s]
05:323:19:22:33
Timestamp [UCT] (epoch)
2019-01-10 21:16:54 (1547155014)
Block
88015 (1512687 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f2d709c69fea71894c910f3c559e668127e25ef58ca6ec515fd94a280a88a250032100268386b33c43b9de0763711fd3a48b96815000072af528ec42cb34ee8c5a78dc021b0000000000000000000000000023f30e0c00000000000000000000
Outputs
1 output(s) for total of 19.432707372 ARQ
stealth address amount amount idx
00: 200f26e180a4cf992384b24eee2f7d4e6043d5519ed1b14c1b7133cad691d13d 19.432707372 434720 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": 88033, 
  "vin": [ {
      "gen": {
        "height": 88015
      }
    }
  ], 
  "vout": [ {
      "amount": 19432707372, 
      "target": {
        "key": "200f26e180a4cf992384b24eee2f7d4e6043d5519ed1b14c1b7133cad691d13d"
      }
    }
  ], 
  "extra": [ 1, 242, 215, 9, 198, 159, 234, 113, 137, 76, 145, 15, 60, 85, 158, 102, 129, 39, 226, 94, 245, 140, 166, 236, 81, 95, 217, 74, 40, 10, 136, 162, 80, 3, 33, 0, 38, 131, 134, 179, 60, 67, 185, 222, 7, 99, 113, 31, 211, 164, 139, 150, 129, 80, 0, 7, 42, 245, 40, 236, 66, 203, 52, 238, 140, 90, 120, 220, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 35, 243, 14, 12, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}