could you add which operating system are you using?
seems it's common for all major versions (win, gnu linux, mac)
but it's a good practice for reporting bugs to include details such operating system
Topic: Transaction time in the cient (Read 1154 times)
For transactions that were already in the blockchain, it should be easy enough to just display the timestamp (formatted properly) of the block in which the Tx was included. It may not be exact (i.e. when the tx was actually broadcast), but it's plenty good enough for display purposes.
I find that the "transaction time" shown in the client is actually the receiving time of the transaction but not the sending time.
When old wallet was opening and downloading new blocks, it shows that there is a new transaction one minute ago, but in fact it was three months ago. This behaviour is really confusing and, even more, it shows ten thousands confirmation for that one minute transaction. I can only go the blockexplorer to find the correct date and remember that this transaction was sent between my wallets. Rescan does not solve this problem. Also, it is a problem that there are no simple way to check this in the client.
I really think the blocking time or sending time should be display in the client instead.
When old wallet was opening and downloading new blocks, it shows that there is a new transaction one minute ago, but in fact it was three months ago. This behaviour is really confusing and, even more, it shows ten thousands confirmation for that one minute transaction. I can only go the blockexplorer to find the correct date and remember that this transaction was sent between my wallets. Rescan does not solve this problem. Also, it is a problem that there are no simple way to check this in the client.
I really think the blocking time or sending time should be display in the client instead.
+1, had to figure that one first time i used the 0.5 client
I find that the "transaction time" shown in the client is actually the receiving time of the transaction but not the sending time.
When old wallet was opening and downloading new blocks, it shows that there is a new transaction one minute ago, but in fact it was three months ago. This behaviour is really confusing and, even more, it shows ten thousands confirmation for that one minute transaction. I can only go the blockexplorer to find the correct date and remember that this transaction was sent between my wallets. Rescan does not solve this problem. Also, it is a problem that there are no simple way to check this in the client.
I really think the blocking time or sending time should be display in the client instead.
When old wallet was opening and downloading new blocks, it shows that there is a new transaction one minute ago, but in fact it was three months ago. This behaviour is really confusing and, even more, it shows ten thousands confirmation for that one minute transaction. I can only go the blockexplorer to find the correct date and remember that this transaction was sent between my wallets. Rescan does not solve this problem. Also, it is a problem that there are no simple way to check this in the client.
I really think the blocking time or sending time should be display in the client instead.
Jump to: