taproot – How this transaction was included within the block if CLTV is way bigger than a present block peak?

taproot – How this transaction was included within the block if CLTV is way bigger than a present block peak?

[ad_1]

So this is transaction in query: 04c2ad1e2ac3651e0cda0d2a3cc4b43434ad45de8330a526ab87aabb67587cc6

It is taproot script is:

OP_PUSHBYTES_32 d4f633eb22227fb319cf064b9f9870123db325999f15ffd2f2c01d653a1a3847
OP_CHECKSIGVERIFY
OP_PUSHBYTES_3 25da0b
OP_CLTV

25da0b equals to 2480651, and it was included in a block with a peak 779883.

How did it occur?

[ad_2]

Deja una respuesta

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *