A Bitcoin transaction can be signed and have a future date without the recipient having received anything. Understanding what’s missing helps avoid confusing a prepared payment with money that has already been sent.
What locktime really limits
In $BTC the nLockTime field, when active, prevents that transaction from being included in a block until a time-based condition is met. It can specify a block height or a time reference.
Here we’re talking about that transaction field. Other mechanisms can prevent an output from being spent through conditions built into the contract itself; not all timelocks work the same way.
A date doesn’t press “send”
The wait expiring does not automatically broadcast the payment. A person, wallet, or service has to communicate the transaction to the network. After that, it still needs to be valid and included by a miner.
Trezor’s documentation makes this clear: it lets you keep the details of a signed transaction with locktime so you can broadcast it when the time comes. Preparing it and broadcasting it are separate steps.
A fictional example
Ana prepares a payment to Luis that can only be included after a future block height. She saves the signed transaction, and no one broadcasts it.
The chain passes that threshold, but Luis still hasn’t received the payment. Meeting the time condition has not communicated the transaction to miners.
Also, nLockTime by itself does not reserve the inputs used. If those same inputs are spent earlier in another confirmed transaction, the prepared payment can no longer use them.
It doesn’t promise an exact minute, either
Height counts blocks, which don’t arrive at fixed intervals. For time-based locks, Bitcoin uses the median timestamp of the previous eleven blocks, according to BIP 113. It doesn’t just look at your phone’s clock.
🛡️ A signed copy may let you broadcast that payment when it becomes valid. It deserves more care than a simple note of intent.
My take: before interpreting “scheduled,” it’s worth distinguishing which condition must be met, who will broadcast the payment, and whether it has already been confirmed.
Sources consulted: 06/11/2026, UTC. Binance Academy — HTLC (timelock context); Bitcoin Developer Guide — Transactions; BIP 113; Trezor — Locktime.
The author may receive rewards from Binance.