The file is timestamped at UTC Date/Time: 2017-10-05 13:51:46 UTC with 3393108 confirmations in block number
2067991
- ID transaction:
fcc5b7...
#ByteStampProof
Prev MD5 HashCash: 6742e688c357b84c8352eb72827dd49d MD5 HashCash: f306e90337936e802cd7d112c2c65bac
This ByteStampMD5: d1ca8667d0c78667134792184952a174
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.