Transaction Details
Tx hash
a61befd864553ae67fde794dc9e4e711c9768d7b3ea6c1ede1f982b62e8e63c0
Tx prefix hash
15754d1cec7e251f48db4f204291ebcb2071d6a817346a619f1502e4ccd10c81
Tx public key
180578cd1c2c0a5a2a91566db812b3acb6cdb7171b4ffcde10f401f6402171f2
Age [y:d:h:m:s]
04:332:14:45:17
Timestamp [UCT] (epoch)
2019-11-03 21:36:12 (1572816972)
Block
299821 (1259146 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01180578cd1c2c0a5a2a91566db812b3acb6cdb7171b4ffcde10f401f6402171f20321003d2f9a9caf9d54f3252d2c88f6c3bb20d6d8530f4055f7cd1eaa4d8ef4d61d9e021b00000000000000000000000000442a35d100000000000000000000
Outputs
1 output(s) for total of 19.938659977 ARQ
stealth address amount amount idx
00: b9edaf48eb1ecc39bfd33b4fc4fef79320e27903d824499ebb29e6e00e8d1801 19.938659977 1353769 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": 299839, 
  "vin": [ {
      "gen": {
        "height": 299821
      }
    }
  ], 
  "vout": [ {
      "amount": 19938659977, 
      "target": {
        "key": "b9edaf48eb1ecc39bfd33b4fc4fef79320e27903d824499ebb29e6e00e8d1801"
      }
    }
  ], 
  "extra": [ 1, 24, 5, 120, 205, 28, 44, 10, 90, 42, 145, 86, 109, 184, 18, 179, 172, 182, 205, 183, 23, 27, 79, 252, 222, 16, 244, 1, 246, 64, 33, 113, 242, 3, 33, 0, 61, 47, 154, 156, 175, 157, 84, 243, 37, 45, 44, 136, 246, 195, 187, 32, 214, 216, 83, 15, 64, 85, 247, 205, 30, 170, 77, 142, 244, 214, 29, 158, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 68, 42, 53, 209, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}