Transaction Details
Tx hash
cb0b693bf0a11f8249744f3d384a0f35314af251d51289fa9079fb1bc4cf0e4e
Tx prefix hash
ed79340c7a8bc810591ab0defded5aec9bc0891cd7011ac79e0e3af33ad112de
Tx public key
9078564199f66cef7af6da4493c6c3ddad0bcb6655bdddc8a871344dff5fa466
Age [y:d:h:m:s]
05:233:04:51:12
Timestamp [UCT] (epoch)
2019-04-11 00:33:15 (1554942795)
Block
152279 (1448089 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019078564199f66cef7af6da4493c6c3ddad0bcb6655bdddc8a871344dff5fa46603210082c33737d45c49293b08a27bde86e8a2d1f8bcd5ffc96a84e83322537779e9ab021b000000000000000000000000000f4f592b00000000000000000000
Outputs
1 output(s) for total of 18.846254114 ARQ
stealth address amount amount idx
00: 35ea19e07ed31802cfdb44de275d3db939841449a5d2b78d6bb5baaeea74b203 18.846254114 696988 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": 152297, 
  "vin": [ {
      "gen": {
        "height": 152279
      }
    }
  ], 
  "vout": [ {
      "amount": 18846254114, 
      "target": {
        "key": "35ea19e07ed31802cfdb44de275d3db939841449a5d2b78d6bb5baaeea74b203"
      }
    }
  ], 
  "extra": [ 1, 144, 120, 86, 65, 153, 246, 108, 239, 122, 246, 218, 68, 147, 198, 195, 221, 173, 11, 203, 102, 85, 189, 221, 200, 168, 113, 52, 77, 255, 95, 164, 102, 3, 33, 0, 130, 195, 55, 55, 212, 92, 73, 41, 59, 8, 162, 123, 222, 134, 232, 162, 209, 248, 188, 213, 255, 201, 106, 132, 232, 51, 34, 83, 119, 121, 233, 171, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 15, 79, 89, 43, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}