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: 19ceb7c71525e3e4f93aa0c4b3dec530745884e857ec91042e35a4aa85386eee
Tx prefix hash: ea3b3ec98a298508851e2419a32c880262ef2c653845c4dabe3da6c27b3b3f6b
Tx public key: 7f44273ca75209903b1a3af77c0bdcf8f86f2773fc3f35a121b3d579a223681c
| Timestamp: 1779713736 | Timestamp [UTC]: 2026-05-25 12:55:36 | Age [y:d:h:m:s]: 00:014:12:40:21 |
| Block: 1602 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6284 | RingCT/type: yes/0 |
| Extra: 017f44273ca75209903b1a3af77c0bdcf8f86f2773fc3f35a121b3d579a223681c020900000001ba6d17be00 | ||
1 output(s) for total of 35.077094573541 HMNY
| stealth address | amount | amount idx | tag |
| 00: 40e138976e3e60c0ca099faef7f0fe00db932f4395882465b59a85afa1de6e77 | 35.077094573541 | 1760 of 0 | <f6> |
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": 1662,
"vin": [ {
"gen": {
"height": 1602
}
}
],
"vout": [ {
"amount": 35077094573541,
"target": {
"tagged_key": {
"key": "40e138976e3e60c0ca099faef7f0fe00db932f4395882465b59a85afa1de6e77",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 127, 68, 39, 60, 167, 82, 9, 144, 59, 26, 58, 247, 124, 11, 220, 248, 248, 111, 39, 115, 252, 63, 53, 161, 33, 179, 213, 121, 162, 35, 104, 28, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}