Bitcoin Forum
November 11, 2024, 08:42:07 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: lock time??  (Read 409 times)
jamyr (OP)
Sr. Member
****
Offline Offline

Activity: 1820
Merit: 373


<------


View Profile
July 15, 2017, 01:34:27 PM
 #1

I just noticed that a lock time shows up in my pending transaction,

  Lock Time Block: 475903


Can anybody tell me what is the significance of this information?

- Bitcointalk Talkshow Video(Aug 2023). Bitcointalk discussion
My bitsler ref link bitsler.com
cpfreeplz
Legendary
*
Offline Offline

Activity: 966
Merit: 1042


View Profile
July 15, 2017, 01:35:50 PM
 #2

What wallet are you using? I've never seen this before and don't really understand what it would be about.

Oh here we go

Quote
Locktime means the transaction may only be accepted by miners until the blockheight indicated in that field has been exceeded.

Since the locktime field indicated 419382 and currently the latest blockheight as of 12th July 2016 1108 (AEST) is 420352 the transaction has now been accepted by the network and confirmation will follow very soon.

https://bitcoin.stackexchange.com/questions/46495/what-does-lock-time-means
jamyr (OP)
Sr. Member
****
Offline Offline

Activity: 1820
Merit: 373


<------


View Profile
July 15, 2017, 01:50:43 PM
 #3

What wallet are you using? I've never seen this before and don't really understand what it would be about.

Oh here we go

Quote
Locktime means the transaction may only be accepted by miners until the blockheight indicated in that field has been exceeded.

Since the locktime field indicated 419382 and currently the latest blockheight as of 12th July 2016 1108 (AEST) is 420352 the transaction has now been accepted by the network and confirmation will follow very soon.

https://bitcoin.stackexchange.com/questions/46495/what-does-lock-time-means

I'm using coins.ph as my receiving address.
Btw this is the tx id:

https://blockchain.info/tx/ee2f08dc039fd7432f216c1011d4338225b5ecfc574044f974146b1ddb573dff

Does this mean my tx will be a bit delayed?
Or normally how long does a block take before its blockheight exceeds?

- Bitcointalk Talkshow Video(Aug 2023). Bitcointalk discussion
My bitsler ref link bitsler.com
HI-TEC99
Legendary
*
Offline Offline

Activity: 2772
Merit: 2846



View Profile
July 15, 2017, 02:13:46 PM
 #4

Your transaction is confirmed now. Its lock time was block 475903 and it was included in block 475912 (nine blocks after its lock time).

You presently need to pay 270 satoshis/byte to get fast confirmations, and your transaction pays 150.29 satoshis/byte, which is about half that fee.

You can find the best fee to pay for your requirements at this site.

https://bitcoinfees.21.co/
ranochigo
Legendary
*
Offline Offline

Activity: 3038
Merit: 4420


Crypto Swap Exchange


View Profile
July 15, 2017, 02:17:50 PM
 #5

I'm using coins.ph as my receiving address.
Receiving wallet doesn't matter, the sending wallet will.
Btw this is the tx id:

https://blockchain.info/tx/ee2f08dc039fd7432f216c1011d4338225b5ecfc574044f974146b1ddb573dff

Does this mean my tx will be a bit delayed?
It really depends. If the nlocktime is in the future, then your transaction cannot be included in any point till after the Unix time or the block time has been reached. Eg. If I set my the nlocktime using time at 1500128161, the transaction cannot be included in blocks that has 1500128150 as the unix time. Similarly, if its set using the block height, I set mine at 475930, it cannot be included in any blocks before that.
Or normally how long does a block take before its blockheight exceeds?
Check the blockchain. You can find the block height there, assuming every block is 10 minutes, it would take 100 minutes for it to potentially get confirmed if the nlocktime is 10 blocks in the future.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
jamyr (OP)
Sr. Member
****
Offline Offline

Activity: 1820
Merit: 373


<------


View Profile
July 15, 2017, 09:26:46 PM
 #6

Your transaction is confirmed now. Its lock time was block 475903 and it was included in block 475912 (nine blocks after its lock time).

You presently need to pay 270 satoshis/byte to get fast confirmations, and your transaction pays 150.29 satoshis/byte, which is about half that fee.

You can find the best fee to pay for your requirements at this site.

https://bitcoinfees.21.co/

Yes 'twas confirmed moments after I posted my reply.(3rd message on this thread).

Also I know the fees and if only Primedice allow a much higher fee, I could have done that.

It really depends. If the nlocktime is in the future, then your transaction cannot be included in any point till after the Unix time or the block time has been reached. Eg. If I set my the nlocktime using time at 1500128161, the transaction cannot be included in blocks that has 1500128150 as the unix time. Similarly, if its set using the block height, I set mine at 475930, it cannot be included in any blocks before that.
Or normally how long does a block take before its blockheight exceeds?
Check the blockchain. You can find the block height there, assuming every block is 10 minutes, it would take 100 minutes for it to potentially get confirmed if the nlocktime is 10 blocks in the future.

I think I'm getting it, though more familiarity is what I need. Thanks for your trouble. Smiley

- Bitcointalk Talkshow Video(Aug 2023). Bitcointalk discussion
My bitsler ref link bitsler.com
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!