<!--{ "name": "BTC.main", "height": 736585, "hash": "000000000000000000047453805dff15189b57656fe1ada8de603a91e75c4ec6", "time": "2022-05-16T06:06:57.885107912Z", "latest_url": "https://api.blockcypher.com/v1/btc/main/blocks/000000000000000000047453805dff15189b57656fe1ada8de603a91e75c4ec6", "previous_hash": "000000000000000000073bdb952221c3f22b621cb58c37d0f90f7c51d7c31276", "previous_url": "https://api.blockcypher.com/v1/btc/main/blocks/000000000000000000073bdb952221c3f22b621cb58c37d0f90f7c51d7c31276", "peer_count": 1044, "unconfirmed_count": 6340, "high_fee_per_kb": 18934, "medium_fee_per_kb": 10318, "low_fee_per_kb": 6520, "last_fork_height": 723102, "last_fork_hash": "00000000000000000006a970fdd8e537521747aff917d909bf3a78b4b68143e1" }
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed immediately.
GUI-related pull requests should be opened against https://github.com/bitcoin-core/gui first. See CONTRIBUTING.md -->
<!-- Please provide clear motivation for your patch and explain how it improves Bitcoin Core user experience or Bitcoin Core developer experience significantly: * Any test improvements or new tests that improve coverage are always welcome. * All other changes should have accompanying unit tests (see `src/test/`) or functional tests (see `test/`). Contributors should note which tests cover modified code. If no tests exist for a region of modified code, new tests should accompany the change. * Bug fixes are most welcome when they come with steps to reproduce or an explanation of the potential issue as well as reasoning for the way the bug was fixed. * Features are welcome, but might be rejected due to design or scope issues. If a feature is based on a lot of dependencies, contributors should first consider building the system outside of Bitcoin Core, if possible. * Refactoring changes are only accepted if they are required for a feature or bug fix or otherwise improve developer experience significantly. For example, most "code style" refactoring changes require a thorough explanation why they are useful, what downsides they have and why they *significantly* improve developer experience or avoid serious programming bugs. Note that code style is often a subjective matter. Unless they are explicitly mentioned to be preferred in the [developer notes](/doc/developer-notes.md), stylistic code changes are usually rejected. -->
<!-- Bitcoin Core has a thorough review process and even the most trivial change needs to pass a lot of eyes and requires non-zero or even substantial time effort to review. There is a huge lack of active reviewers on the project, so patches often sit for a long time. -->