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: 404a206369129e49f53d30eb51e3674f8809360ec6c6c3d664e6bde75b2490c0
Tx prefix hash: ec9b2a26bb8a5a4f3525647237ae27ca595574652ce86de0b2546f8fae319196
Tx public key: 793c6c4ecf6237e70bdd8b9af2b39a7f2b10e71d13f07a800d7f7485f1db7ae2
| Timestamp: 1780051421 | Timestamp [UTC]: 2026-05-29 10:43:41 | Age [y:d:h:m:s]: 00:010:17:07:17 |
| Block: 4403 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3549 | RingCT/type: yes/0 |
| Extra: 01793c6c4ecf6237e70bdd8b9af2b39a7f2b10e71d13f07a800d7f7485f1db7ae202090000000326697be300 | ||
1 output(s) for total of 34.890195293298 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6c515eb2f19210f59bf634fda9c6593006cd0db5ffbf8dc42890b38d6b8f4356 | 34.890195293298 | 5508 of 0 | <db> |
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": 4463,
"vin": [ {
"gen": {
"height": 4403
}
}
],
"vout": [ {
"amount": 34890195293298,
"target": {
"tagged_key": {
"key": "6c515eb2f19210f59bf634fda9c6593006cd0db5ffbf8dc42890b38d6b8f4356",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 121, 60, 108, 78, 207, 98, 55, 231, 11, 221, 139, 154, 242, 179, 154, 127, 43, 16, 231, 29, 19, 240, 122, 128, 13, 127, 116, 133, 241, 219, 122, 226, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}