Summary

There is currently no easy/fast way to find the corresponding receive block of a specific send block by using the available RPCs. The only method I could think of is to request ALL blocks of the receiving account and iterate through them, which sounds like something that should be rather done on node side than on client side; due to performance reasons.

This issue could be solved by adding a receive_hash option to the blocks_info RPC. In contrast to the source_account option (which adds the address of the send block to its corresponding receive block), the receive_hash option would add the hash of the receive block to its corresponding send block.

What problem would be solved by this feature?

Complicated additional client processing logic to find receive blocks by their send block hash could/should be avoided as well as unnecessary HTTP traffic and resulting delays.

Are there any previous requests for this feature?

Not that I'm aware of.

Do you have a suggested solution?

Yes.

If this feature is approved, would you be willing to submit a pull request with the solution?

I would

Possible solution

I will create a PR.

Supporting files

No response