Transaction Details
Tx hash
82c2a8e2392d77e0834a578bc01dbe30bd743ebb769a8d7c8e508cf484ac5a39
Tx prefix hash
422c33badfea27f0b9957171272d20c8dbb2756dcd281c561f1b9f19e244f69f
Tx public key
40c7a221a03b0e21e820541852f6a5f65085f3a1fc8c1a6a020cc3f2a991d848
Age [y:d:h:m:s]
05:280:20:55:07
Timestamp [UCT] (epoch)
2019-02-20 00:59:20 (1550624360)
Block
116716 (1482010 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0140c7a221a03b0e21e820541852f6a5f65085f3a1fc8c1a6a020cc3f2a991d84803210075590a74a8fe4b60ec47c7e038465a0f8a14aa33df953710dfdeacaac6d36f4e021b00000000000000000000000000456adb0b00000000000000000000
Outputs
1 output(s) for total of 19.168569188 ARQ
stealth address amount amount idx
00: c7fa9c65aec95140fef49ac46ec495e021f5a96993615e4fa64aae41e7dc6199 19.168569188 567512 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": 116734, 
  "vin": [ {
      "gen": {
        "height": 116716
      }
    }
  ], 
  "vout": [ {
      "amount": 19168569188, 
      "target": {
        "key": "c7fa9c65aec95140fef49ac46ec495e021f5a96993615e4fa64aae41e7dc6199"
      }
    }
  ], 
  "extra": [ 1, 64, 199, 162, 33, 160, 59, 14, 33, 232, 32, 84, 24, 82, 246, 165, 246, 80, 133, 243, 161, 252, 140, 26, 106, 2, 12, 195, 242, 169, 145, 216, 72, 3, 33, 0, 117, 89, 10, 116, 168, 254, 75, 96, 236, 71, 199, 224, 56, 70, 90, 15, 138, 20, 170, 51, 223, 149, 55, 16, 223, 222, 172, 170, 198, 211, 111, 78, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 69, 106, 219, 11, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}