Transaction Details
Tx hash
cccd563222136c3ff17b04d1763596b5f671d0bf334dbf78318e79259231447a
Tx prefix hash
54149a0082dbe43c46281522cb53f7093716f8bbec79d9de27be09aa6b431268
Tx public key
0229a58b4bafc023485e45af3487c4424c630fb9dc73e5050a6723d38085f624
Age [y:d:h:m:s]
05:294:13:48:18
Timestamp [UCT] (epoch)
2018-12-17 19:36:10 (1545075370)
Block
70937 (1492144 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
010229a58b4bafc023485e45af3487c4424c630fb9dc73e5050a6723d38085f62403210075f20f1b4f13ca60e765895c7520e37f13990e4fbe8e6f31193cbc4e6a87e3e80210000000831f0801000000000100000024
Outputs
1 output(s) for total of 19.591602301 ARQ
stealth address amount amount idx
00: aa4ce5ce4675ac46a8bb0c95374453b86d710e4f3b95164e1b542e0545bd6573 19.591602301 369771 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": 70955, 
  "vin": [ {
      "gen": {
        "height": 70937
      }
    }
  ], 
  "vout": [ {
      "amount": 19591602301, 
      "target": {
        "key": "aa4ce5ce4675ac46a8bb0c95374453b86d710e4f3b95164e1b542e0545bd6573"
      }
    }
  ], 
  "extra": [ 1, 2, 41, 165, 139, 75, 175, 192, 35, 72, 94, 69, 175, 52, 135, 196, 66, 76, 99, 15, 185, 220, 115, 229, 5, 10, 103, 35, 211, 128, 133, 246, 36, 3, 33, 0, 117, 242, 15, 27, 79, 19, 202, 96, 231, 101, 137, 92, 117, 32, 227, 127, 19, 153, 14, 79, 190, 142, 111, 49, 25, 60, 188, 78, 106, 135, 227, 232, 2, 16, 0, 0, 0, 131, 31, 8, 1, 0, 0, 0, 0, 1, 0, 0, 0, 36
  ], 
  "rct_signatures": {
    "type": 0
  }
}