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: 1be427753a224d64b678ec2148b65efcd09cf823f8a6e29a4dc0e8cb13f8060c
Tx prefix hash: 87811153b42af7626f9ba4bf8969bc5e1c4052ee65b2e87aa0919c871ef95330
Tx public key: f37535eaabf03c0627a7b799496b021fbd73329e0559ca1d8bb7a47180797596
| Timestamp: 1779513418 | Timestamp [UTC]: 2026-05-23 05:16:58 | Age [y:d:h:m:s]: 00:017:11:52:05 |
| Block: 675 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8060 | RingCT/type: yes/0 |
| Extra: 01f37535eaabf03c0627a7b799496b021fbd73329e0559ca1d8bb7a471807975960208b158d12eec3291ad | ||
1 output(s) for total of 35.139169732738 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0613fe37ac3df3ca3a4c85c44d3fc649c57c7477c595683a03b0574cdac95439 | 35.139169732738 | 744 of 0 | <33> |
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": 735,
"vin": [ {
"gen": {
"height": 675
}
}
],
"vout": [ {
"amount": 35139169732738,
"target": {
"tagged_key": {
"key": "0613fe37ac3df3ca3a4c85c44d3fc649c57c7477c595683a03b0574cdac95439",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 243, 117, 53, 234, 171, 240, 60, 6, 39, 167, 183, 153, 73, 107, 2, 31, 189, 115, 50, 158, 5, 89, 202, 29, 139, 183, 164, 113, 128, 121, 117, 150, 2, 8, 177, 88, 209, 46, 236, 50, 145, 173
],
"rct_signatures": {
"type": 0
}
}