3 Latests blocks
Block #[height]
Previous block hash Nonce Merkle root tree Timestamp Difficulty Block sizeLimitations
Lack of transactions details
My VPS (2GB RAM) does not seem powerful enough to process so much data; ~2000 transactions per block for which the associated data would need to be retrieved, processed, and serialized. The reverse proxy and a few other services must also be taken into account. I tried to enable this feature on the RPC getblock function via the verbosity=2 parameter. This seems to have saturated the Docker container and its volume, preventing me from restarting the container because it was using up RAM and was then killed by the host. I would have loved to display the data inside the transactions so that I could explore the blockchain in depth. In particular, the messages left by users in OP_RETURN.
API rate limit
As I explained above, my VPS is limited. I have therefore set up a rate limit of 10 requests per second to avoid overloading my server.
Slow API response
Always the same reason: 2GB RAM.
RAM efficiency
For your reference, here is an extract of my bitcoin.conf to reduce RAM usage as much as possible. Please note that some settings may change the behavior of your node. Here are two useful documents that I found during my research: Bitcoin Stack Exchange - How to run node bitcoind in a low memory environment and Github Bitcoin Doc - Reduce Memory.
prune=550
dbcache=4
maxorphantx=10
maxconnections=12
maxsigcachesize=4
rpcthreads=1
disablewallet=1
maxmempool=50