Transaction Details
Tx hash
a8f56012faa84c3436adce1868dd078e0cbd312b8daec36dc92007fdca00f366
Tx prefix hash
65735881f1740723a51ca69f6627195de4681187764480f5e8ee258bba5fd053
Tx public key
1cfe63ee38dc8f733fbdb3ddffcbe7853eb1045b8a416007db63adf2c300508d
Age [y:d:h:m:s]
05:311:20:45:08
Timestamp [UCT] (epoch)
2019-01-22 22:09:41 (1548194981)
Block
96643 (1504116 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011cfe63ee38dc8f733fbdb3ddffcbe7853eb1045b8a416007db63adf2c300508d032100e4c607445faace43765960439fb9dce5f223e6c06e46ec0457c0ececd96caaee021b0000000000000000000000000010b8486d00000000000000000000
Outputs
1 output(s) for total of 19.352922497 ARQ
stealth address amount amount idx
00: b632f62c0d81e12fb54df496a852ddbabbc309f1b1028238215dd042dcc9d273 19.352922497 476965 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": 96661, 
  "vin": [ {
      "gen": {
        "height": 96643
      }
    }
  ], 
  "vout": [ {
      "amount": 19352922497, 
      "target": {
        "key": "b632f62c0d81e12fb54df496a852ddbabbc309f1b1028238215dd042dcc9d273"
      }
    }
  ], 
  "extra": [ 1, 28, 254, 99, 238, 56, 220, 143, 115, 63, 189, 179, 221, 255, 203, 231, 133, 62, 177, 4, 91, 138, 65, 96, 7, 219, 99, 173, 242, 195, 0, 80, 141, 3, 33, 0, 228, 198, 7, 68, 95, 170, 206, 67, 118, 89, 96, 67, 159, 185, 220, 229, 242, 35, 230, 192, 110, 70, 236, 4, 87, 192, 236, 236, 217, 108, 170, 238, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 16, 184, 72, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}