Transaction Details
Tx hash
ef9576784d262b0d86a2ceb1c63f1286628712006533f21e89f9cf396041c34c
Tx prefix hash
dcf1c6c37b30115a1a0413d8393f6fab449811efceb20e0764287fa1a2477737
Tx public key
91b9fbea9c54ab3adcbd7ac10f889640ee4233eaa87f757cc93a8bb3fb9b0207
Age [y:d:h:m:s]
05:189:06:26:39
Timestamp [UCT] (epoch)
2019-05-21 23:57:48 (1558483068)
Block
181597 (1416677 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0191b9fbea9c54ab3adcbd7ac10f889640ee4233eaa87f757cc93a8bb3fb9b0207032100d5e570757d6514dfe8ba4bf349cbfa7f5efd5cc76234e836dd51a0f810de0f02021b000000000000000000000000000f34b8e900000000000000000000
Outputs
1 output(s) for total of 18.584618166 ARQ
stealth address amount amount idx
00: 89d3412af3cf04df88e879400af050b2f8bd469f8e8476c91c1ef38157bcd726 18.584618166 817804 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": 181615, 
  "vin": [ {
      "gen": {
        "height": 181597
      }
    }
  ], 
  "vout": [ {
      "amount": 18584618166, 
      "target": {
        "key": "89d3412af3cf04df88e879400af050b2f8bd469f8e8476c91c1ef38157bcd726"
      }
    }
  ], 
  "extra": [ 1, 145, 185, 251, 234, 156, 84, 171, 58, 220, 189, 122, 193, 15, 136, 150, 64, 238, 66, 51, 234, 168, 127, 117, 124, 201, 58, 139, 179, 251, 155, 2, 7, 3, 33, 0, 213, 229, 112, 117, 125, 101, 20, 223, 232, 186, 75, 243, 73, 203, 250, 127, 94, 253, 92, 199, 98, 52, 232, 54, 221, 81, 160, 248, 16, 222, 15, 2, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 15, 52, 184, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}