Transaction Details
Tx hash
488f43e9a33beb2868d3409a3f3c4fec3f4ca308da0d5abe26609bb37b408286
Tx prefix hash
632425ed5990ef4e0ae9e1df1a1195e6b25e02b28f8e06d0c9624c5ed14d468e
Tx public key
6ed9c3e5a9ae2843b5b4867b69aec9d61b479b72eb957c7ecfc8584b83025705
Age [y:d:h:m:s]
05:151:08:41:37
Timestamp [UCT] (epoch)
2019-05-02 05:36:51 (1556775411)
Block
167459 (1390161 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016ed9c3e5a9ae2843b5b4867b69aec9d61b479b72eb957c7ecfc8584b83025705032100364823ae26ff4c3e455dfdc3e6ca14a03caeac6e4b77e3bc20924a28117cbb6c021b000000000000000000000000006e01d3b100000000000000000000
Outputs
1 output(s) for total of 18.710330110 ARQ
stealth address amount amount idx
00: c5f2a7d7d704e552c1a6684d5d1236267ed2238df0e0492067c943ef7ba8fb9b 18.710330110 762114 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": 167477, 
  "vin": [ {
      "gen": {
        "height": 167459
      }
    }
  ], 
  "vout": [ {
      "amount": 18710330110, 
      "target": {
        "key": "c5f2a7d7d704e552c1a6684d5d1236267ed2238df0e0492067c943ef7ba8fb9b"
      }
    }
  ], 
  "extra": [ 1, 110, 217, 195, 229, 169, 174, 40, 67, 181, 180, 134, 123, 105, 174, 201, 214, 27, 71, 155, 114, 235, 149, 124, 126, 207, 200, 88, 75, 131, 2, 87, 5, 3, 33, 0, 54, 72, 35, 174, 38, 255, 76, 62, 69, 93, 253, 195, 230, 202, 20, 160, 60, 174, 172, 110, 75, 119, 227, 188, 32, 146, 74, 40, 17, 124, 187, 108, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 110, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}