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: 79e5ee56db772c1cb969bb4fc79fd106ba14345137aa8d2e885e4a8b7e94d53a
Tx prefix hash: ba2286382b4d3179b9a5448595d21bbea737ff9822cb7f289376463bf996215f
Tx public key: b88844357a496754a22f6178f2b44abfa2ae8ae1d9f793200359cff8a83a6cfc
| Timestamp: 1780137269 | Timestamp [UTC]: 2026-05-30 10:34:29 | Age [y:d:h:m:s]: 00:009:12:44:24 |
| Block: 4972 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2914 | RingCT/type: yes/0 |
| Extra: 01b88844357a496754a22f6178f2b44abfa2ae8ae1d9f793200359cff8a83a6cfc02090000000426697be300 | ||
1 output(s) for total of 34.852350118233 HMNY
| stealth address | amount | amount idx | tag |
| 00: 63bea0c138b5b10756e9a956a82fad228ec75f7aef1eb6c7e8949d57810d40e1 | 34.852350118233 | 6325 of 0 | <aa> |
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": 5032,
"vin": [ {
"gen": {
"height": 4972
}
}
],
"vout": [ {
"amount": 34852350118233,
"target": {
"tagged_key": {
"key": "63bea0c138b5b10756e9a956a82fad228ec75f7aef1eb6c7e8949d57810d40e1",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 184, 136, 68, 53, 122, 73, 103, 84, 162, 47, 97, 120, 242, 180, 74, 191, 162, 174, 138, 225, 217, 247, 147, 32, 3, 89, 207, 248, 168, 58, 108, 252, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}