Switch to ArdorForum

I suspect that the apparent discrepancy may have to do with the fact that these two transactions are asset exchange order placements. So things would happen in this sequence:

1) The place order transaction is broadcasted
2) The block including the transaction is generated, confirming the order placement
3) The order is matched and executed

Then the timestamp in the database would be the moment where the order was executed, later than the time when the block including the place order transaction was generated.

Transaction timestamps are allowed to drift up to 15 seconds after the block timestamp. To accommodate differences in clocks I guess.

No changes about that recently - it's coming from the initial version by BCNext - see https://bitbucket.org/JeanLucPicard/nxt-public/src/4af2d32ada1b62e0a348809612ee0ed35b49c353/Nxt.java?at=master&fileviewer=file-view-default#Nxt.java-1012 (he checks that transaction is not 15 seconds after curTime, later, in Feb 2014, was added a check that it is not 15 seconds after the block timestamp)

Could you please help me figure out, on these screenshots we see that 2 accounts broadcasted transactions: 1st trans at 17:26:04 from account NXT-GWL5-AWWX-YNRH-859XF and 2nd trans at 17:26:05 from account NXT-5ERP-RQNA-J84F-34LTY. Transaction which was executed is the second one which was broadcasted later. So the questions are 1. how could this happen? 2. what are the actual execution rules? 3. what actually dates mean? Thats not the only example i noticed so far, it happens regulary (with bigger gap, like ~3seconds) so there must be some rule and/or explanation.