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: 8abe5afc34c76cc2445ec3eff137a19bd8a01dcf6f2444f051f340ac1a819345
Tx prefix hash: 803fc4c3f4b933929b51fea927b370bffe109b926d070d7af4e8e1df6d6c17fb
Tx public key: 0a5c77c32169fb3c6cfde26c4486eac524acc06bb1eb9c6b7211ea881be8522c
| Timestamp: 1779480438 | Timestamp [UTC]: 2026-05-22 20:07:18 | Age [y:d:h:m:s]: 00:017:01:04:49 |
| Block: 645 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7241 | RingCT/type: yes/0 |
| Extra: 010a5c77c32169fb3c6cfde26c4486eac524acc06bb1eb9c6b7211ea881be8522c02090000000293369e7d00 | ||
1 output(s) for total of 35.141180471603 HMNY
| stealth address | amount | amount idx | tag |
| 00: a5364eb0306db0e3862e3e75247ad21cef7472ade5f07e83038e23db6d51cd82 | 35.141180471603 | 688 of 0 | <bb> |
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": 705,
"vin": [ {
"gen": {
"height": 645
}
}
],
"vout": [ {
"amount": 35141180471603,
"target": {
"tagged_key": {
"key": "a5364eb0306db0e3862e3e75247ad21cef7472ade5f07e83038e23db6d51cd82",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 10, 92, 119, 195, 33, 105, 251, 60, 108, 253, 226, 108, 68, 134, 234, 197, 36, 172, 192, 107, 177, 235, 156, 107, 114, 17, 234, 136, 27, 232, 82, 44, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}