TX Broadcast timestamp | Bitcointalksearch.org

albert0bsd

hero member

Activity: 862

Merit: 662

Quote from: nc50lc on August 24, 2023, 10:25:50 AM

Try Blockcypher's API.
Their blockexplorer has a simple "x hours/days/months ago" message but the API call for "txs" has 'received' timestamp which is when they've received the transaction into their mempool.

Thank you so much Exactly what i am looking for

Quote from: logfiles on August 24, 2023, 09:40:52 AM

Any reason you need to know the exact time a transaction was broadcasted? Because I personally don't see any use case Tongue

I agree with you, usually that information is worthless, but i get some curious about some transactions the other day and i am doing some research, if you are interesting i can let you know when i publish it.

Regards!

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

Quote from: albert0bsd on August 24, 2023, 09:41:53 AM

Ok guys thank you for your replies, i am NOT looking for the Exact time... I just want to know if there are another page that show the time of "first sight of some TX time".

Try Blockcypher's API.
Their blockexplorer has a simple "x hours/days/months ago" message but the API call for "txs" has 'received' timestamp which is when they've received the transaction into their mempool.

For example: https://api.blockcypher.com/v1/btc/main/txs/29dd0ce748f0489d1aece0282f2b2031fcb31fbdf0d70fece99e56fc5702a6e5?

Code:

"confirmed": "2023-07-06T16:19:51Z",
"received": "2023-07-06T16:05:21.536Z",

albert0bsd

hero member

Activity: 862

Merit: 662

Ok guys thank you for your replies, i am NOT looking for the Exact time... I just want to know if there are another page that show the time of "first sight of some TX time".

What i want is to know another source of that information without matter how acurate or inacurate it is... i am pretty aware of the network propagate time and network issues like those that were mentioned.

Thank you.

logfiles

copper member

Activity: 2198

Merit: 1837

🌀 Cosmic Casino

Remember it's a network of nodes and not just 1 node. The time it will take for the broadcasted transaction information to reach a blockchain.com explore node vs mempool.space node will most likely vary.

The lock time information is what matters.

Any reason you need to know the exact time a transaction was broadcasted? Because I personally don't see any use case Tongue

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

There is no way of finding out and the transaction broadcast timing. The timing that you see is basically the timing for which it is seen by any of Blockchain.com's node. This can be wildly inaccurate depending on the extent and the speed of propagation.

For certain transactions which are not very well broadcasted, the timing will be inaccurate depending on when the node sees it.

Even the block timestamp is not accurate. Blocks can drift from the network adjusted time by quite a significant amount. There is no way to enforce accuracy of timings on the blockchain.

Findingnemo

hero member

Activity: 2366

Merit: 793

Bitcoin = Financial freedom

AFAIK, there is no way to find the exact broadcast time of a transaction in the Bitcoin network.

The broadcast timestamp you see on your wallet interface is just an estimation because the time taken for your node to propagate to other nodes across the network depends on factors like network congestion, latency, and the number of hops it takes to reach different nodes.

albert0bsd

hero member

Activity: 862

Merit: 662

Hi I just wonder if there are any other site where we can check the broadcast time of a TX.

For example i know that blockchain.com store that information for example for TX
12f34b58b04dfb0233ce889f674781c0e0c7ba95482cca469125af41a78d13b3

Code:

Broadcasted on 16 Apr 2023 12:23:05 GMT-6

But mempool.space replace that informaction with the mined block timestamp

Code:

Timestamp ‎2023-04-16 00:29

So the questions is if there any other site that store that information.

Regards!

Topic: TX Broadcast timestamp (Read 135 times)