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: 98cc61adf5fde7c1993cfada0e49c65bc53c1a06baaa5f44297b6d7bda6e9df0
Tx prefix hash: ddecb76fd84e3d7946907cde8d464b384de4a655899255e33d83aaa7e03ac247
Tx public key: 1e366a47ea8a9877841d3f852ef945410db599011dce2177a14bd6b15882c317
| Timestamp: 1779434790 | Timestamp [UTC]: 2026-05-22 07:26:30 | Age [y:d:h:m:s]: 00:017:18:09:27 |
| Block: 101 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7785 | RingCT/type: yes/0 |
| Extra: 011e366a47ea8a9877841d3f852ef945410db599011dce2177a14bd6b15882c317020900000001a662ed0300 | ||
1 output(s) for total of 35.177661836106 HMNY
| stealth address | amount | amount idx | tag |
| 00: cb22a660b1e48eb28309c1fbb21fa91c6f09b4ed7bd3aeaa6883d61d3f1ac760 | 35.177661836106 | 97 of 0 | <a5> |
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": 161,
"vin": [ {
"gen": {
"height": 101
}
}
],
"vout": [ {
"amount": 35177661836106,
"target": {
"tagged_key": {
"key": "cb22a660b1e48eb28309c1fbb21fa91c6f09b4ed7bd3aeaa6883d61d3f1ac760",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 30, 54, 106, 71, 234, 138, 152, 119, 132, 29, 63, 133, 46, 249, 69, 65, 13, 181, 153, 1, 29, 206, 33, 119, 161, 75, 214, 177, 88, 130, 195, 23, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}