Transaction date changed

[RapTarX]

Sorry if I'm being bored to you since I have already created another thread last hour for another query. I have a pending tx more than a week (can't remember certain date). To check when I did release the tx, I went to blockchain.com explorer and found that tx date has been shown as todays date.
I guess I have understood the reason in one way (a logical thought in my mind). It's kind of rebroadcast?
What's the technical explanation behind the date? It should be around 15th July while it's showing 24th July.

[1714978999]

1714978999

[1714978999]

1714978999

[1714978999]

1714978999

[1714978999]

1714978999

[jackg]

It's probably a bug with blockchain.com. I don't think it's possible to change the data a transaction has been made without resigning it and the default for a lot of wallets is using the current block height rather than the date.

[RapTarX]

It's probably a bug with blockchain.com.

I guess no because it's same as of blockchain.com in blockcypher as well- https://live.blockcypher.com/btc/tx/c84c28331d96c39a681caea0e5e7940bf0c3aca56f8fbcf95d45bfc9fe3d9468/
I have done nothing after releasing the tx a week ago. Using electrum wallet. There's something which rebroadcast/resigning the tx automatically? I don't know. I have no idea about this.

[ryzaadit]

-snip-

I checked the hash transaction from "Blockchair" the time stamp of the transaction was made from 7 days ago

2020-07-18 03:39(7 days ago)

https://blockchair.com/bitcoin/transaction/c84c28331d96c39a681caea0e5e7940bf0c3aca56f8fbcf95d45bfc9fe3d9468

I think some explorer transaction provider using a different timestamp, this thread could be help if you want to know the reason : https://bitcoin.stackexchange.com/questions/49210/timestamp-different-block-explorers-are-not-the-same

[BitMaxz]

I have done nothing after releasing the tx a week ago. Using electrum wallet. There's something which rebroadcast/resigning the tx automatically? I don't know. I have no idea about this.

If you are using Electrum then it's not rebroadcasting automatically you will need to manually rebroadcast the transaction by copying the raw transaction.

So you might be worried about your transaction and you think it will keep rebroadcast and stuck on the nodes forever?


Why not make a double-spend transaction instead and increase the transaction fee. The network right now is too congested and even https://coinb.in/#fees wouldn't recommend 1 sat/byte fee.

Look at this topic "TUTORIAL - How to fix Unconfirmed Transactions!"

[JeromeTash]

Given that your transaction was sent out about a week ago, it means that I went through the weekend without getting confirmed, Weekend is always considered to be the time when the bitcoin fees is at its lowest. Fortunately I had my 2 sats/byte transaction get confirmed on Monday morning this very week (My Tx would also be stuck if it was 1 sat/byte).

I would suggest you bump the fee to the range of 10 sats/byte since it RBF enabled if you want it to stand some chance of getting confirmed this weekend. Your transaction size isn't that big. It's only 192 bytes, that should bring the fee to around 0.0000111 BTC (around $0.1 at the current rate) if you bumped it to 10 sats/byte

[Ryker1]

Well, most likely after 7 days of unconfirmed the bitcoin network will reject your transaction and it will back to your wallet. ^[AFAIK]
If you are also using an Electrum wallet you can replace the fee, because a low fee, while the network is congested, will take too much time for your transaction to be confined. Unless, if you did not in a hurry.
You can see here I quoted.

basically you are better off letting Electrum decide, you can also set it on mempool fee estimation

Go to ^{[Tools - Preferences - Fees - Enable Replace-by-Fee]}

[nc50lc]

I guess I have understood the reason in one way (a logical thought in my mind). It's kind of rebroadcast?
What's the technical explanation behind the date? It should be around 15th July while it's showing 24th July.

Well, the unconfirmed transaction itself doesn't contain any timestamp, just 'locktime' if your client set it to the current block height.
If your transaction has a locktime not set to 0x00000000, check that block height's timestamp and that's the original broadcast date of your transaction.
Use other blockexplorer to check the 'locktime'.

My theory: it looks like it was already dropped by most nodes must be because it was way past their mempool size limit and more higher fee transactions were prioritized.
Some nodes must have kept it and blockchain.com and others received it again from them, making the received time the current date.
Blockcypher for example, currently doesn't have the transaction in their mempool/database.

[odolvlobo]

Sorry if I'm being bored to you since I have already created another thread last hour for another query. I have a pending tx more than a week (can't remember certain date). To check when I did release the tx, I went to blockchain.com explorer and found that tx date has been shown as todays date.
I guess I have understood the reason in one way (a logical thought in my mind). It's kind of rebroadcast?
What's the technical explanation behind the date? It should be around 15th July while it's showing 24th July.

A transaction does not have a timestamp. Therefore, the time shown by the site is probably the time when it received the transaction. I think you are right about the time changing because the transaction was rebroadcasted, but you can't know for sure without asking the site what the time means.

[RapTarX]

The issue isn't about tx being unconfirmed nor about bumping the fee. I'm well aware of such things. Only nc50lc got me here. I wanted to know the technical aspect of different dates in explorer which doesn't fit the actual date of the tx.