For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: abdc7e3f61e8f21dad81404a3d283b7a29a25e9a1ad6387af71d78f2af249f43
Tx prefix hash: 15bebd9b61210c0ccc82fcefb158f889e38d93c14a29de7f71a435edb94089ac
Tx public key: 0a55e20eb658ef401bba146e54fcde60a6f5fa8376766acc985b824f5c7ef254
| Timestamp: 1779466731 | Timestamp [UTC]: 2026-05-22 16:18:51 | Age [y:d:h:m:s]: 00:017:08:27:56 |
| Block: 519 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7367 | RingCT/type: yes/0 |
| Extra: 010a55e20eb658ef401bba146e54fcde60a6f5fa8376766acc985b824f5c7ef25402090000000293369e7d00 | ||
1 output(s) for total of 35.149626831356 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16a08220e300fc9beeb9d280d05e29fda823ac81fe4462243ab01fbcd66eb1b4 | 35.149626831356 | 523 of 0 | <19> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 579,
"vin": [ {
"gen": {
"height": 519
}
}
],
"vout": [ {
"amount": 35149626831356,
"target": {
"tagged_key": {
"key": "16a08220e300fc9beeb9d280d05e29fda823ac81fe4462243ab01fbcd66eb1b4",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 10, 85, 226, 14, 182, 88, 239, 64, 27, 186, 20, 110, 84, 252, 222, 96, 166, 245, 250, 131, 118, 118, 106, 204, 152, 91, 130, 79, 92, 126, 242, 84, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}