user78997: For example, if I run bx base58check-decode with the base58 encoded private key of Kxj5ejwPg2s2ejZHW7N1zAydD4fkmFi9j19QRmgeVK9mXL3wFMmp from this example, I get the following:

{
    checksum 2274467570
    payload 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b982401
    version 128
}
The payload, as well as the version, make sense to me; however, if I convert the checksum to a hex, it doesn't match the checksum of F29E9187 that I'm expecting, i.e., I understand how to form it per this question. But I don't understand how 2274467570 and F29E9187 are related.

user38482: decimal to hex, and then reversed ordering:
$ echo "obase=16;2274467570" | bc
87919EF2

reversed:
87 91 9E F2 -> F2 9E 91 87

78997: <p>For example, if I run <code>bx base58check-decode</code> with the base58 encoded private key of <code>Kxj5ejwPg2s2ejZHW7N1zAydD4fkmFi9j19QRmgeVK9mXL3wFMmp</code> from this <a href="https://royalforkblog.github.io/2014/08/11/graphical-address-generator/#hello" rel="nofollow noreferrer">example</a>, I get the following:</p>

<p><code>
{
    checksum 2274467570
    payload 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b982401
    version 128
}</code></p>

<p>The payload, as well as the version, make sense to me; however, if I convert the checksum to a hex, it doesn't match the checksum of F29E9187 that I'm expecting, i.e., I understand how to form it per this <a href="https://bitcoin.stackexchange.com/questions/51970/how-to-generate-a-bitcoin-private-key-checksum">question</a>. But I don't understand how 2274467570 and F29E9187 are related.</p>
 38482: <p>decimal to hex, and then reversed ordering:</p>

<pre><code>$ echo "obase=16;2274467570" | bc
87919EF2
</code></pre>

<p>reversed:
87 91 9E F2 -> F2 9E 91 87</p>
