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: 9135267f597fc965912e668933ef4ac7cfca8b41cea2a67d37e21906fa81c63b
Tx prefix hash: 9bbf68c30190ae93a036a5d099db92ab4c02b865a0f7a735f70f8c523d3a8f43
Tx public key: 5b8683c79d11b72979382c4be71bf58e3b13c6a0f6ce2a4e3a6b4a2305ba51a4
| Timestamp: 1780077647 | Timestamp [UTC]: 2026-05-29 18:00:47 | Age [y:d:h:m:s]: 00:010:06:46:00 |
| Block: 4720 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3166 | RingCT/type: yes/0 |
| Extra: 015b8683c79d11b72979382c4be71bf58e3b13c6a0f6ce2a4e3a6b4a2305ba51a402090000000226697be300 | ||
1 output(s) for total of 34.872527207516 HMNY
| stealth address | amount | amount idx | tag |
| 00: 819be59bb4d791636d68a5c6bfb9fa101d525e12caa78483915eec1177b579a5 | 34.872527207516 | 5930 of 0 | <5a> |
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": 4780,
"vin": [ {
"gen": {
"height": 4720
}
}
],
"vout": [ {
"amount": 34872527207516,
"target": {
"tagged_key": {
"key": "819be59bb4d791636d68a5c6bfb9fa101d525e12caa78483915eec1177b579a5",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 91, 134, 131, 199, 157, 17, 183, 41, 121, 56, 44, 75, 231, 27, 245, 142, 59, 19, 198, 160, 246, 206, 42, 78, 58, 107, 74, 35, 5, 186, 81, 164, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}