<p>"time" is a Unix epoch time when the transaction was added to the wallet</p>

<p>"receivedtime" is A Unix epoch time when the transaction was detected by the local node or the time of the block on the local best blockchain that included the transaction. Not returned to move category payments</p>

CC BY-SA 3.0
2018-01-04T16:42:04.733Z
I understand, but why is the time that is being returned by bitcoind different from what it was last week?
ImJustACowLol
CC BY-SA 3.0
2018-01-04T16:51:44.337Z
Does your computer time change?
Tailer
CC BY-SA 3.0
2018-01-04T17:38:10.283Z
no, my computer time hasn't changed.
ImJustACowLol
CC BY-SA 3.0
2018-01-04T17:47:55.043Z
Could you send TXID?
Tailer
CC BY-SA 3.0
2018-01-05T09:55:23.547Z
0efb691a93a17ea4253a25a51a081918a73bc09366ae8dfaed6c28098f2eaf02 , on online trackers it also shows the 4th of january. I suppose that the code I use isn't showing earlier transactions for whatever reason. I'll dig into it some further :)
ImJustACowLol
CC BY-SA 3.0
2018-01-04T16:31:25.783Z
2018-01-04T16:31:25.783Z
Tailer
<p>I've got a small question: over a week ago I did some transactions on the Bitcoin testnet as I am developing a new GUI header for full nodes. When continuing development today, I noticed that when running the command 'listtransactions' the fields 'time' and 'timereceived' are different from what they were last week.</p>

<p>When checking the transaction ID on <a href="https://www.blocktrail.com/tBTC" rel="nofollow noreferrer">this website</a>, it shows the date corresponding with what I receive when using listtransactions. </p>

<p>Can anyone explain to me why the time/timereceived fields changed and why they are so far off from when I actually did the transaction? </p>

<p>Some additional info:</p>

<ul>
<li>I started my node on the testnet today for the first time since a
week </li>
<li>Actual transaction happened last week on (I think) tuesday
around 13:00 Amsterdam time</li>
</ul>

CC BY-SA 3.0
2018-01-04T22:46:32.273Z
What are the values for `time` and `timereceived` and what do you think they should be?
Ava Chow
<bitcoind><timestamp><time><listtransactions>
Bitcoind Testnet time/timereceived constantly changing?
ImJustACowLol
# Bitcoind Testnet time/timereceived constantly changing?

(Asked by: username_0 on 2018-01-04)

I've got a small question: over a week ago I did some transactions on the Bitcoin testnet as I am developing a new GUI header for full nodes. When continuing development today, I noticed that when running the command 'listtransactions' the fields 'time' and 'timereceived' are different from what they were last week.

When checking the transaction ID on [this website](https://www.blocktrail.com/tBTC), it shows the date corresponding with what I receive when using listtransactions.

Can anyone explain to me why the time/timereceived fields changed and why they are so far off from when I actually did the transaction?

Some additional info:

* I started my node on the testnet today for the first time since a
  week
* Actual transaction happened last week on (I think) tuesday
  around 13:00 Amsterdam time

**Tags:** bitcoind, timestamp, time, listtransactions

> **Comments:**
> **username_1**: What are the values for `time` and `timereceived` and what do you think they should be?  

---

## 1 answers

### Answer by username_2 on 2018-01-04. Score: 0

"time" is a Unix epoch time when the transaction was added to the wallet

"receivedtime" is A Unix epoch time when the transaction was detected by the local node or the time of the block on the local best blockchain that included the transaction. Not returned to move category payments

> **Comments:**
> **username_0**: I understand, but why is the time that is being returned by bitcoind different from what it was last week?  
> **username_2**: Does your computer time change?  
> **username_0**: no, my computer time hasn't changed.  
> **username_2**: Could you send TXID?  
> **username_0**: 0efb691a93a17ea4253a25a51a081918a73bc09366ae8dfaed6c28098f2eaf02 , on online trackers it also shows the 4th of january. I suppose that the code I use isn't showing earlier transactions for whatever reason. I'll dig into it some further :)  

---

