Transaction with an unlock_time has 0 as tx_confirmations and tx_timestamp in the outputs endpoint
For a locked transaction with an unlock_time set, in the outputs endpoint the "tx_confirmations" is 0 and the "tx_timestamp" is 0, but in the transaction endpoint the "confirmations" is 218170 and the timestamp is 1668901942. Is there a reason for that or is it a bug?