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: 66ccf01365864403424e49457579064c7c1ed88106182000d98f1366b180ddb8
Tx prefix hash: 778a01253e61d7a5259a3cc74170b69f70084b2a7634971bb6541efa3a11fc9e
Tx public key: 75148b6a269c26962a3f1d8bb2535c394d8b4c595c5862b4109a8a994e197f46
| Timestamp: 1779450122 | Timestamp [UTC]: 2026-05-22 11:42:02 | Age [y:d:h:m:s]: 00:017:15:07:46 |
| Block: 314 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7587 | RingCT/type: yes/0 |
| Extra: 0175148b6a269c26962a3f1d8bb2535c394d8b4c595c5862b4109a8a994e197f460209000000054438f87f00 | ||
1 output(s) for total of 35.163373263262 HMNY
| stealth address | amount | amount idx | tag |
| 00: bcc896e35e61b9c005ba5f0df211ea3e415fa783e35d659014534e5f9ec78ba0 | 35.163373263262 | 310 of 0 | <9f> |
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": 374,
"vin": [ {
"gen": {
"height": 314
}
}
],
"vout": [ {
"amount": 35163373263262,
"target": {
"tagged_key": {
"key": "bcc896e35e61b9c005ba5f0df211ea3e415fa783e35d659014534e5f9ec78ba0",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 117, 20, 139, 106, 38, 156, 38, 150, 42, 63, 29, 139, 178, 83, 92, 57, 77, 139, 76, 89, 92, 88, 98, 180, 16, 154, 138, 153, 78, 25, 127, 70, 2, 9, 0, 0, 0, 5, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}