Inconsistent pagination behavior in v2 xpub endpoint

[avoloshko]

The following txids are returned for vpub5ZbEbAb1g4HMzYbxVj8tbWTjUUDkaRmp3qaQZDqHaHrJAobkvhXUB9BmgtdFAaFgfSTawDCVWccgw9DnN6cLK28zNLyJxEjvKuv8W9dqFJj

["b7a9c32218e1a33b40062f188c6ceafd2182b502779433fa2f2679cbf357208c","5e21743f5c4a8a94b4e0ca47adc6bfc96a3f01aa92c2c9a5ffe3f2f807aea4ad"]

https://blockstream.info/testnet/search?q=b7a9c32218e1a33b40062f188c6ceafd2182b502779433fa2f2679cbf357208c
https://blockstream.info/testnet/search?q=5e21743f5c4a8a94b4e0ca47adc6bfc96a3f01aa92c2c9a5ffe3f2f807aea4ad

Expected Behavior
When requesting a specific number of transactions via the pageSize parameter, the API should strictly adhere to this limit.

Actual Behavior
The API returns more transactions than specified by the pageSize parameter. This behavior is consistent across various settings of pageSize. Moreover, the additional transaction does not exist.