We have recently started using OpenZeppelin TransparentUpgradeableProxy contracts for our upgradeable contracts. Previously we used the OpenZeppelin AdminiUpgradeabilityProxy and blockscout autoamtically recognized the bytecode of those contracts as being proxies and showed the proxy UI for the contract. However, for the newer TransparentUpgradeableProxy contracts, blockscout does not seem to recognize these contracts as being proxy contracts. An example is this contract: Contract 0x959CF9c3f8bDdba69210159c25f77BCE58EADC75 - POA Sokol Explorer This is a contract that uses OpenZeppelin TransparentUpgradeableProxy as described in this post Verify hardhat upgradeable proxy on blockscout - Upgrades - OpenZeppelin Community. Is there a means by which blockscout can recognize these contracts as being proxies?