Transaction Details
Tx hash
38fc149b2ec1994db21f8c99a712dc97582ee320c591c44e91c169ecd8a61c2b
Tx prefix hash
77ace3db703c075cef85baad1d0133db03b88d46bf47031122548fb48242bfe3
Tx public key
39861b04e92c156e245c74aad0dc95c989b50ee055275ba1f23707e6db367b91
Age [y:d:h:m:s]
05:067:11:45:47
Timestamp [UCT] (epoch)
2019-08-02 08:44:41 (1564735481)
Block
233444 (1329972 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0139861b04e92c156e245c74aad0dc95c989b50ee055275ba1f23707e6db367b910321003b8e30e3351771bd0dd0dc827197a785a6220ed056ce8387a53508571d8aa552021b00000000000000000000000002f87975fa00000000000000000000
Outputs
1 output(s) for total of 18.130791418 ARQ
stealth address amount amount idx
00: 5387d8b6d1b8bbf2e4007f05091e5ac4691aaaae7b4dbf0056ea379e7cca5e58 18.130791418 1082278 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": 233462, 
  "vin": [ {
      "gen": {
        "height": 233444
      }
    }
  ], 
  "vout": [ {
      "amount": 18130791418, 
      "target": {
        "key": "5387d8b6d1b8bbf2e4007f05091e5ac4691aaaae7b4dbf0056ea379e7cca5e58"
      }
    }
  ], 
  "extra": [ 1, 57, 134, 27, 4, 233, 44, 21, 110, 36, 92, 116, 170, 208, 220, 149, 201, 137, 181, 14, 224, 85, 39, 91, 161, 242, 55, 7, 230, 219, 54, 123, 145, 3, 33, 0, 59, 142, 48, 227, 53, 23, 113, 189, 13, 208, 220, 130, 113, 151, 167, 133, 166, 34, 14, 208, 86, 206, 131, 135, 165, 53, 8, 87, 29, 138, 165, 82, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 248, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}