Transaction Details
Tx hash
8901c85fdbfd765e53998b9bb41d2fd61ea936431316b216b3aaa8c191e6c299
Tx prefix hash
527d7fc658e079713ce2c6b93e22c8f6c34bc321443386615e4f8a797b6f079f
Tx public key
8b1a0cfb980e2c1404631f5ae4e4f0b47db6d29a6525d4e8caae2de0711edbdc
Age [y:d:h:m:s]
05:297:14:59:23
Timestamp [UCT] (epoch)
2018-12-15 05:34:05 (1544852045)
Block
69058 (1494359 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
018b1a0cfb980e2c1404631f5ae4e4f0b47db6d29a6525d4e8caae2de0711edbdc0321009b9b3c90c24fb7a1f08e0c3f525491aab81608e00d2e15bf530f5b42a4fd91b7021000000172170801000000000000000000
Outputs
1 output(s) for total of 19.609163797 ARQ
stealth address amount amount idx
00: de507f9caead9329f2b232133f3521a23dc5c02a5d2bbbbb064a34a0bf4b0d0e 19.609163797 362053 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": 69076, 
  "vin": [ {
      "gen": {
        "height": 69058
      }
    }
  ], 
  "vout": [ {
      "amount": 19609163797, 
      "target": {
        "key": "de507f9caead9329f2b232133f3521a23dc5c02a5d2bbbbb064a34a0bf4b0d0e"
      }
    }
  ], 
  "extra": [ 1, 139, 26, 12, 251, 152, 14, 44, 20, 4, 99, 31, 90, 228, 228, 240, 180, 125, 182, 210, 154, 101, 37, 212, 232, 202, 174, 45, 224, 113, 30, 219, 220, 3, 33, 0, 155, 155, 60, 144, 194, 79, 183, 161, 240, 142, 12, 63, 82, 84, 145, 170, 184, 22, 8, 224, 13, 46, 21, 191, 83, 15, 91, 66, 164, 253, 145, 183, 2, 16, 0, 0, 1, 114, 23, 8, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}