steem-engine api history order problem for multiple txs in one block

Words
123
Reading
1 min
Listen
Play
7y

I've been worrying about this edge case, and it turns out that it's actually random.

For instance, in block 1896844,
https://steem-engine.rocks/b/1896844

there are two txs of steemfinex@steemfinex (this is a very rare case and thank you for using it :)

when history is called, it returns the order randomly.

Same block, so timestamp is the same, so no way to distinguish. no tx order is returned, so no way to sort.

Any other way to resolve this than fetching the block?
=> my solution is adding txid as the second sorting key

Hopefully, the order will be fixed.


스팀엔진 api history가져올때 같은 블록에 한 계정 여러 트랜잭션이 있으면 history api로는 소팅할 방법이 없는 문제가 있습니다. 블록에는 순서가 할당되어있긴한데 history에서는 현재 해결이 안 됩니다.

steem-engine api history order problem for multiple txs in one bloc... | Ecency