Transaction Details
Tx hash
430b77c5e5cb3ec1edd4fe2f47f4b3cabf5472f78515e8a9c2c40ef169f2adbd
Tx prefix hash
9e2a30abfcc5fd5f35a8a03d47ce24b39027cd7ce7265094ced5c54b699c66a5
Tx public key
0f9841f59b8d01f27a589be727e015a5c939f0f7ed75c77dd4a589f56b87af0d
Age [y:d:h:m:s]
05:142:23:30:09
Timestamp [UCT] (epoch)
2019-05-18 03:54:19 (1558151659)
Block
178840 (1384060 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010f9841f59b8d01f27a589be727e015a5c939f0f7ed75c77dd4a589f56b87af0d03210033c214d48593f919a6c1888455c9353c428cb8f6eac5231e057d7ebbc1bc34aa021b00000000000000000000000000d801d3b100000000000000000000
Outputs
1 output(s) for total of 18.609066322 ARQ
stealth address amount amount idx
00: 468dadeb5652b1f4f6dd679474f9527c871aa58c2234a24d015a94c69c2c5db0 18.609066322 806923 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": 178858, 
  "vin": [ {
      "gen": {
        "height": 178840
      }
    }
  ], 
  "vout": [ {
      "amount": 18609066322, 
      "target": {
        "key": "468dadeb5652b1f4f6dd679474f9527c871aa58c2234a24d015a94c69c2c5db0"
      }
    }
  ], 
  "extra": [ 1, 15, 152, 65, 245, 155, 141, 1, 242, 122, 88, 155, 231, 39, 224, 21, 165, 201, 57, 240, 247, 237, 117, 199, 125, 212, 165, 137, 245, 107, 135, 175, 13, 3, 33, 0, 51, 194, 20, 212, 133, 147, 249, 25, 166, 193, 136, 132, 85, 201, 53, 60, 66, 140, 184, 246, 234, 197, 35, 30, 5, 125, 126, 187, 193, 188, 52, 170, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 216, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}