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: b91b725c04a56315cc72d21bee764872c78ff0f7813775e675185cc5c71019b6
Tx prefix hash: 9e9d917a7c784b213935da3a067e1111faf79fcf0771a0f4c6c2f67e9170a4ed
Tx public key: 83cbbe28b62769c77862a44e8ebac3d2f5f9b5b51c9997bb0acb5ff979895581
| Timestamp: 1780061990 | Timestamp [UTC]: 2026-05-29 13:39:50 | Age [y:d:h:m:s]: 00:010:09:39:03 |
| Block: 4534 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3352 | RingCT/type: yes/0 |
| Extra: 0183cbbe28b62769c77862a44e8ebac3d2f5f9b5b51c9997bb0acb5ff97989558102090000000226697be300 | ||
1 output(s) for total of 34.881478616633 HMNY
| stealth address | amount | amount idx | tag |
| 00: 11d23c63d042f4baedafefe5404b83385ff8f3ccf921f28e68a02160acedc176 | 34.881478616633 | 5689 of 0 | <9e> |
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": 4594,
"vin": [ {
"gen": {
"height": 4534
}
}
],
"vout": [ {
"amount": 34881478616633,
"target": {
"tagged_key": {
"key": "11d23c63d042f4baedafefe5404b83385ff8f3ccf921f28e68a02160acedc176",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 131, 203, 190, 40, 182, 39, 105, 199, 120, 98, 164, 78, 142, 186, 195, 210, 245, 249, 181, 181, 28, 153, 151, 187, 10, 203, 95, 249, 121, 137, 85, 129, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}