Transaction Details
Tx hash
ebb6300b1ed15dabaddcf0fa35c12bcf663d1b18c54fd167c58435afb926dea9
Tx prefix hash
996e0dda3a73631dac7c922b35fabd2ad5803853039483a15ed53c0fdfd792d3
Tx public key
bcd66e8be881a197317170ffe014f8510521c99cd3568b282b497e2ef0b039f1
Age [y:d:h:m:s]
05:303:05:43:01
Timestamp [UCT] (epoch)
2019-01-31 02:32:26 (1548901946)
Block
102462 (1497990 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bcd66e8be881a197317170ffe014f8510521c99cd3568b282b497e2ef0b039f1032100e2e6a8d9b60f1be93f2bc9cd0f0ae866a6846df99a524c3c854d7d23a597ed19021b000000000000000000000000001a7097c700000000000000000000
Outputs
1 output(s) for total of 19.299390702 ARQ
stealth address amount amount idx
00: b1bda1e0c61f4a09ba756c27762784181380ece312105149b7b25f51e807463a 19.299390702 506022 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": 102480, 
  "vin": [ {
      "gen": {
        "height": 102462
      }
    }
  ], 
  "vout": [ {
      "amount": 19299390702, 
      "target": {
        "key": "b1bda1e0c61f4a09ba756c27762784181380ece312105149b7b25f51e807463a"
      }
    }
  ], 
  "extra": [ 1, 188, 214, 110, 139, 232, 129, 161, 151, 49, 113, 112, 255, 224, 20, 248, 81, 5, 33, 201, 156, 211, 86, 139, 40, 43, 73, 126, 46, 240, 176, 57, 241, 3, 33, 0, 226, 230, 168, 217, 182, 15, 27, 233, 63, 43, 201, 205, 15, 10, 232, 102, 166, 132, 109, 249, 154, 82, 76, 60, 133, 77, 125, 35, 165, 151, 237, 25, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 26, 112, 151, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}