Any ideas about this one? I've imported addresses into my wallet and on rescan, all transactions come up as same date and time?

  • 3
    The transaction data in the blockchain doesn't have timestamps, but the client knows when it sent a transaction so that is what normally will be added to the transaction. Since the client is learning of these transactions from the blockchain, perhaps the block timestamp should be used instead of the time the rescan occurs. Commented Apr 18, 2013 at 0:35
  • Ah, thanks. Yeah I'm surprised it doesn't use the block timestamp in the case of rescanning. Oh well... version 0.9 ?!
    – pinhead
    Commented Apr 18, 2013 at 0:39
  • 2
    @StephenGornick post it as an answer! Commented Apr 18, 2013 at 7:29
  • Shouldn't this be considered a bug? I can see a very valid case for opening a request for change to the Qt client!
    – Joe Pineda
    Commented Jan 21, 2014 at 3:27

1 Answer 1


I've also had the same issue whereby importing a private key using RPC Console importprivkey will rescan and tag it with the time which the rescan takes place in btc-qt.

Even Multibit which uses the following format for private key (*.key) files is only dated such that the date corresponds to what is assumed to be the key's creation date: Kwnononok7xQwSNIPSNIPSNIPSNIPssthcheckth1s 2013-09-18T09:42:28Z

As mentioned, the Blockchain is not being consulted for transaction history - a major flaw IMO.

  • 1
    I just ran into this again today! Commented Jan 27, 2019 at 2:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.