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: 9316c13706cc28f6bbcdc0d5b3ae8f5f6297120db8d59ff0d2c10a6bbaf5f91e
Tx prefix hash: e87c1725bb1acdd881a291b50369738cfaaea707aa07761e749e5bd5eeafb270
Tx public key: 1d805030b462fba2182a83ab1dd9498301960afd402ef9fd15ca4230aa1bd1e5
| Timestamp: 1779631531 | Timestamp [UTC]: 2026-05-24 14:05:31 | Age [y:d:h:m:s]: 00:015:11:30:26 |
| Block: 913 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6973 | RingCT/type: yes/0 |
| Extra: 011d805030b462fba2182a83ab1dd9498301960afd402ef9fd15ca4230aa1bd1e5020900000001ba6d17be00 | ||
1 output(s) for total of 35.123221947474 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7d3d7db709c66d81490fccd955bfbaceeb2da673cb929ad9e779ea425169ff8 | 35.123221947474 | 1047 of 0 | <1e> |
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": 973,
"vin": [ {
"gen": {
"height": 913
}
}
],
"vout": [ {
"amount": 35123221947474,
"target": {
"tagged_key": {
"key": "d7d3d7db709c66d81490fccd955bfbaceeb2da673cb929ad9e779ea425169ff8",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 29, 128, 80, 48, 180, 98, 251, 162, 24, 42, 131, 171, 29, 217, 73, 131, 1, 150, 10, 253, 64, 46, 249, 253, 21, 202, 66, 48, 170, 27, 209, 229, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}