The last few days [SteemSQL Wrapper](https://sql.steemhelpers.com) had some problems with displaying the delay — it just did not load and SteemSQL Wrapper always displays `Delay: loading...`, if you did use API then you were getting `504 Gateway Time-out`.

It was caused because of steemd.steemit.com [was deprecated](https://steemit.com/steemitdev/@steemitdev/last-chance-to-update-steemd-steemit-com-will-be-retired-on-january-6) on 6th of January. I used steem-python to get the last block from the blockchain but it uses steemd as a default node. This problem can be easily solved by setting [a custom node](https://www.steem.center/index.php?title=Public_Websocket_Servers). But while I did search a reason for the problem, I decided full remove steem-python from the project.

![image.png](https://res.cloudinary.com/hpiynhbhq/image/upload/v1515507776/ndevf350elk7fbp71rsx.png)

In fact, it was a bad solution — checking the time of the last block in SteemSQL and comparing it with current time is enough because Steem gets a new block every 3 seconds.

A quotation from the White Paper:
> Because the active witnesses are known in advance, Steem is able to schedule witnesses to produce blocks every 3 seconds.

So now this part of the project is optimized and now you can get the delay info faster.

[Commit](https://github.com/sihaelov/steemsql-wrapper/commit/cdd4bb409b782cc40e236c35f614fcafb6f40cd6)

![image](https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/U5dtgf6jjoQQJeK4B9jSWsNxkYFrzQo_1680x8400)

<br /><hr/><em>Posted on <a href="https://utopian.io/utopian-io/@emptyname/steemsql-wrapper-fixed-and-optimized-the-delay-info">Utopian.io -  Rewarding Open Source Contributors</a></em><hr/>