Transaction Details
Tx hash
90258d53c079da6cccd6a683efd02003dcc54c499008f295e1e2458ac33e85d8
Tx prefix hash
fb2f0693e30e36ebc75b41da011f814fcdef7fa228afaddcdc76e4ec854f8a94
Tx public key
790daa5b5d924f1a5fab143b3eec9277928f77212d169ee919363c56c026047a
Age [y:d:h:m:s]
05:345:12:04:50
Timestamp [UCT] (epoch)
2018-12-20 00:11:22 (1545264682)
Block
72513 (1528056 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01790daa5b5d924f1a5fab143b3eec9277928f77212d169ee919363c56c026047a0321007feebc3f788f134f7ceaeaec736ef4e20eed477636d451e796f290a7af22c7e9021b000000000000000000000000002a04ce8700000000000000000000
Outputs
1 output(s) for total of 19.576884830 ARQ
stealth address amount amount idx
00: da0538d46ae1701d405d90bffeadb82790eef3b818061fe042830d5a55e2b15c 19.576884830 374426 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": 72531, 
  "vin": [ {
      "gen": {
        "height": 72513
      }
    }
  ], 
  "vout": [ {
      "amount": 19576884830, 
      "target": {
        "key": "da0538d46ae1701d405d90bffeadb82790eef3b818061fe042830d5a55e2b15c"
      }
    }
  ], 
  "extra": [ 1, 121, 13, 170, 91, 93, 146, 79, 26, 95, 171, 20, 59, 62, 236, 146, 119, 146, 143, 119, 33, 45, 22, 158, 233, 25, 54, 60, 86, 192, 38, 4, 122, 3, 33, 0, 127, 238, 188, 63, 120, 143, 19, 79, 124, 234, 234, 236, 115, 110, 244, 226, 14, 237, 71, 118, 54, 212, 81, 231, 150, 242, 144, 167, 175, 34, 199, 233, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 42, 4, 206, 135, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}