The file is timestamped at UTC Date/Time: 2017-09-29 17:29:43 UTC with 3414662 confirmations in block number
2057065
- ID transaction:
3d11ad...
#ByteStampProof
Prev MD5 HashCash: a5cd2464959c9e34fec394c8e614cce2 MD5 HashCash: 0c3a01556812383b12ff37e6f3668de3
When you upload a file to ByteSt@mp, it goes through three phases:
1) if just uploaded, it is in queue to be recorded in the BlockChain (or waiting your payment)
2) then it becomes recorded in BlockChain at some Transaction ID, but it is not yet confirmed by any miner.
3) at last it becomes confirmed . Only at this point it has a timestamp.
To see the registration progress you have to click the above link several times, waiting a few minutes between one and the other.
Or you can upload the same file again and again.
After the phase 3, you can see that the number of confirmation grows. The more the confirmations, more reliable is the timestamp.
If there are very low confirmations and there are network problems, the timestamp could change of few minutes.
The time it takes depends on the time taken by the miners from around the world to solve the block.
We cannot do anything to speed up the process.
But it is precisely the fact of having to wait a few minutes that gives us a reliable timestamp.