Transaction Details
Tx hash
a719b6fe2e4669ea7e50ea9d5f583842f7d9b4b249d4f90fbe36b924ed4d6046
Tx prefix hash
8349c4ba02fc27df219fa7f5cdf40a1d147a26465bf8f56c2521340c40e22af5
Tx public key
dc8c541eb35f1694bfac1d328c30fc3d1b5d5ddd2efd9fbffc94d9efa2404bae
Age [y:d:h:m:s]
05:126:21:35:08
Timestamp [UCT] (epoch)
2019-07-23 23:46:19 (1563925579)
Block
226643 (1372071 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01dc8c541eb35f1694bfac1d328c30fc3d1b5d5ddd2efd9fbffc94d9efa2404bae032100d18c7a2dcb50c32dd03a22f232e80fa7ad0d9fc17fe06a5b3896dd9e8b438555021b000000000000000000000000009fc4c81900000000000000000000
Outputs
1 output(s) for total of 18.189684479 ARQ
stealth address amount amount idx
00: c12044e5b2bcf7d5a8999f2ea74e0efdd54003c712076826b7ff05033fb28730 18.189684479 1062405 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": 226661, 
  "vin": [ {
      "gen": {
        "height": 226643
      }
    }
  ], 
  "vout": [ {
      "amount": 18189684479, 
      "target": {
        "key": "c12044e5b2bcf7d5a8999f2ea74e0efdd54003c712076826b7ff05033fb28730"
      }
    }
  ], 
  "extra": [ 1, 220, 140, 84, 30, 179, 95, 22, 148, 191, 172, 29, 50, 140, 48, 252, 61, 27, 93, 93, 221, 46, 253, 159, 191, 252, 148, 217, 239, 162, 64, 75, 174, 3, 33, 0, 209, 140, 122, 45, 203, 80, 195, 45, 208, 58, 34, 242, 50, 232, 15, 167, 173, 13, 159, 193, 127, 224, 106, 91, 56, 150, 221, 158, 139, 67, 133, 85, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 159, 196, 200, 25, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}