Transaction Details
Tx hash
98ade749958dfa63dbff35ed4beec3696e6439b538e1c377f886d9a492f95732
Tx prefix hash
3b0f4ffe4a10ca4609c92e91eb2ce4dc4f6e8f9fda18564b1065f920a62b95a7
Tx public key
3cc016d5ca505e8f0690a5e375863ef56be351ce6058693c80267d7160b596a6
Age [y:d:h:m:s]
05:117:02:17:32
Timestamp [UCT] (epoch)
2019-08-01 21:30:40 (1564695040)
Block
233102 (1364970 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013cc016d5ca505e8f0690a5e375863ef56be351ce6058693c80267d7160b596a60321009c2fd7808597e5958a07d6cadc1489d30341706e2fd86670e1e743d646bc5a57021b00000000000000000000000004abedcd2100000000000000000000
Outputs
1 output(s) for total of 18.133791959 ARQ
stealth address amount amount idx
00: cca0141a7d8a838d1de692fe15c43c8fcda8374d46c841e7f7a1f973cc75e7bb 18.133791959 1081512 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": 233120, 
  "vin": [ {
      "gen": {
        "height": 233102
      }
    }
  ], 
  "vout": [ {
      "amount": 18133791959, 
      "target": {
        "key": "cca0141a7d8a838d1de692fe15c43c8fcda8374d46c841e7f7a1f973cc75e7bb"
      }
    }
  ], 
  "extra": [ 1, 60, 192, 22, 213, 202, 80, 94, 143, 6, 144, 165, 227, 117, 134, 62, 245, 107, 227, 81, 206, 96, 88, 105, 60, 128, 38, 125, 113, 96, 181, 150, 166, 3, 33, 0, 156, 47, 215, 128, 133, 151, 229, 149, 138, 7, 214, 202, 220, 20, 137, 211, 3, 65, 112, 110, 47, 216, 102, 112, 225, 231, 67, 214, 70, 188, 90, 87, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 171, 237, 205, 33, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}