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: 712d68d7def6582649b37db91e69681ba083f6bcf24df7c29a0dffa071429142
Tx prefix hash: 2405f9db7b32c428d8f42be6348b254a69b1cc0297c0a66d555107335c022198
Tx public key: f41776651117b4890f19fd5ee301ed971469e68034f894b1dcecc576a6518dde
| Timestamp: 1779434533 | Timestamp [UTC]: 2026-05-22 07:22:13 | Age [y:d:h:m:s]: 00:017:15:56:40 |
| Block: 91 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7795 | RingCT/type: yes/0 |
| Extra: 01f41776651117b4890f19fd5ee301ed971469e68034f894b1dcecc576a6518dde020900000001a662ed0300 | ||
1 output(s) for total of 35.178332803797 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0431bd0e2652c18121ce98b9629cecb2d24dff5b00ceb9273e9be02bcb39874f | 35.178332803797 | 87 of 0 | <f4> |
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": 151,
"vin": [ {
"gen": {
"height": 91
}
}
],
"vout": [ {
"amount": 35178332803797,
"target": {
"tagged_key": {
"key": "0431bd0e2652c18121ce98b9629cecb2d24dff5b00ceb9273e9be02bcb39874f",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 244, 23, 118, 101, 17, 23, 180, 137, 15, 25, 253, 94, 227, 1, 237, 151, 20, 105, 230, 128, 52, 248, 148, 177, 220, 236, 197, 118, 166, 81, 141, 222, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}