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: fba8822d8b809fda37a023486defaa029456c552b0b1ebce58836a47e145bf53
Tx prefix hash: 56db47e32c1f95451f57fdd50c871828c273af8fd96d44e985ea44bed05d074b
Tx public key: dd0ee7d7e46687aecfb07f53fb07d84a86cd256ebcbeee364eef37bc1ab9bbb5
| Timestamp: 1779719772 | Timestamp [UTC]: 2026-05-25 14:36:12 | Age [y:d:h:m:s]: 00:014:10:59:45 |
| Block: 1733 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6153 | RingCT/type: yes/0 |
| Extra: 01dd0ee7d7e46687aecfb07f53fb07d84a86cd256ebcbeee364eef37bc1ab9bbb5020900000001ba6d17be00 | ||
1 output(s) for total of 35.068331203511 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6222be539062f6db614365576e579b5dc0b7fa4382457e403163be0ec93280bd | 35.068331203511 | 1909 of 0 | <61> |
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": 1793,
"vin": [ {
"gen": {
"height": 1733
}
}
],
"vout": [ {
"amount": 35068331203511,
"target": {
"tagged_key": {
"key": "6222be539062f6db614365576e579b5dc0b7fa4382457e403163be0ec93280bd",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 221, 14, 231, 215, 228, 102, 135, 174, 207, 176, 127, 83, 251, 7, 216, 74, 134, 205, 37, 110, 188, 190, 238, 54, 78, 239, 55, 188, 26, 185, 187, 181, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}