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: 319dc75c11318aa3dfbecbecc47593b420774c85b49c9b8971fdf6c8693ee4fb
Tx prefix hash: 19232e75468a33eb9aeb4a4e6ae03e9abce2caf90aa02d3dcd654704a0e07838
Tx public key: 45d020092c0b9672e8d597aab3b34d4cb618b0eb2d5108218d9f2c6b0c85cc17
| Timestamp: 1779636527 | Timestamp [UTC]: 2026-05-24 15:28:47 | Age [y:d:h:m:s]: 00:015:10:07:10 |
| Block: 1122 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6764 | RingCT/type: yes/0 |
| Extra: 0145d020092c0b9672e8d597aab3b34d4cb618b0eb2d5108218d9f2c6b0c85cc17020900000001ba6d17be00 | ||
1 output(s) for total of 35.109223348545 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c1104821b3864f0c07fbf05eae1296386ff3e131bb36a83b1cb3a6f833936cb | 35.109223348545 | 1262 of 0 | <a1> |
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": 1182,
"vin": [ {
"gen": {
"height": 1122
}
}
],
"vout": [ {
"amount": 35109223348545,
"target": {
"tagged_key": {
"key": "8c1104821b3864f0c07fbf05eae1296386ff3e131bb36a83b1cb3a6f833936cb",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 69, 208, 32, 9, 44, 11, 150, 114, 232, 213, 151, 170, 179, 179, 77, 76, 182, 24, 176, 235, 45, 81, 8, 33, 141, 159, 44, 107, 12, 133, 204, 23, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}