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: 41c9041939e455f44e9ac48566e282f8a2752dc76a5be2980f3cd3a9af3cab12
Tx prefix hash: 33f4bded21477dcb9b85abf50fafe6b494b5af2078159a90615d4826cd4c5686
Tx public key: 0c336ba4c740283a56dfda45f1dc38ea9851eacfd2c0a7c6d7c7f3909729abe8
| Timestamp: 1779795716 | Timestamp [UTC]: 2026-05-26 11:41:56 | Age [y:d:h:m:s]: 00:013:13:54:01 |
| Block: 2265 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5621 | RingCT/type: yes/0 |
| Extra: 010c336ba4c740283a56dfda45f1dc38ea9851eacfd2c0a7c6d7c7f3909729abe802090000000126697be300 | ||
1 output(s) for total of 35.039362649439 HMNY
| stealth address | amount | amount idx | tag |
| 00: 705ba4f3871efd06941944703f2b30575d549009ccaf003cf65d9e9e0289aa08 | 35.039362649439 | 2631 of 0 | <9b> |
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": 2325,
"vin": [ {
"gen": {
"height": 2265
}
}
],
"vout": [ {
"amount": 35039362649439,
"target": {
"tagged_key": {
"key": "705ba4f3871efd06941944703f2b30575d549009ccaf003cf65d9e9e0289aa08",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 12, 51, 107, 164, 199, 64, 40, 58, 86, 223, 218, 69, 241, 220, 56, 234, 152, 81, 234, 207, 210, 192, 167, 198, 215, 199, 243, 144, 151, 41, 171, 232, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}