Transaction Details
Tx hash
2d8e0769451a1174ef1e079dca5250d636c45b908a10763dd66aa219b01631b1
Tx prefix hash
4da284e1eac5f45d7ec5af0ce06c7f608a87ecd22b41344b9d00e6c457c000fb
Tx public key
1fbb0a0771e8badcb9fc4e8c2284b3b426bdc3ddaecc0549da9a9dd8cc32b5a7
Age [y:d:h:m:s]
05:041:17:21:18
Timestamp [UCT] (epoch)
2019-10-19 03:03:09 (1571454189)
Block
288604 (1311489 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
011fbb0a0771e8badcb9fc4e8c2284b3b426bdc3ddaecc0549da9a9dd8cc32b5a702110000001fd6db947100000000000000000003210087378b255efb31812b74d3d00b40bdb0e4e8d8c78513f1838e1d2f7fdb8b1be0
Outputs
1 output(s) for total of 20.045637118 ARQ
stealth address amount amount idx
00: bb886c5386e4fa9e50dc7fece36e2ea2ae6d59f2c6f1af336d50408a25a67441 20.045637118 1301677 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": 288622, 
  "vin": [ {
      "gen": {
        "height": 288604
      }
    }
  ], 
  "vout": [ {
      "amount": 20045637118, 
      "target": {
        "key": "bb886c5386e4fa9e50dc7fece36e2ea2ae6d59f2c6f1af336d50408a25a67441"
      }
    }
  ], 
  "extra": [ 1, 31, 187, 10, 7, 113, 232, 186, 220, 185, 252, 78, 140, 34, 132, 179, 180, 38, 189, 195, 221, 174, 204, 5, 73, 218, 154, 157, 216, 204, 50, 181, 167, 2, 17, 0, 0, 0, 31, 214, 219, 148, 113, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 135, 55, 139, 37, 94, 251, 49, 129, 43, 116, 211, 208, 11, 64, 189, 176, 228, 232, 216, 199, 133, 19, 241, 131, 142, 29, 47, 127, 219, 139, 27, 224
  ], 
  "rct_signatures": {
    "type": 0
  }
}