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: 91b5a04bbd3fcf08e0d6d9ac1792010d8b30531674f7a75a6c920ca6114ef600
Tx prefix hash: 46f6b2005fae8b5fb9f5cbd82383431ea32c5c24a6ce7987c6bacec910c5c468
Tx public key: a12f009ce3af8d9c51de9bce842daf80327b8b5970ade7fb445c2bf739aee7d8
| Timestamp: 1779964423 | Timestamp [UTC]: 2026-05-28 10:33:43 | Age [y:d:h:m:s]: 00:011:15:02:14 |
| Block: 3790 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4096 | RingCT/type: yes/0 |
| Extra: 01a12f009ce3af8d9c51de9bce842daf80327b8b5970ade7fb445c2bf739aee7d802090000000326697be300 | ||
1 output(s) for total of 34.958411370422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1f585acf02e7a6a2d63283e55706d5295e9122641aa39b3e699b856b943d385e | 34.958411370422 | 4603 of 0 | <1b> |
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": 3850,
"vin": [ {
"gen": {
"height": 3790
}
}
],
"vout": [ {
"amount": 34958411370422,
"target": {
"tagged_key": {
"key": "1f585acf02e7a6a2d63283e55706d5295e9122641aa39b3e699b856b943d385e",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 161, 47, 0, 156, 227, 175, 141, 156, 81, 222, 155, 206, 132, 45, 175, 128, 50, 123, 139, 89, 112, 173, 231, 251, 68, 92, 43, 247, 57, 174, 231, 216, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}