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: 995e2acb3273763d9ae18921ab1d559d011bc0f06ac20d906e1463fae7ace7f5
Tx prefix hash: 5c59836009a76d9dfe149d4ebf024b4d6ed80ead1fe3a615dd7e1939835d2af0
Tx public key: d866b1f3d2487255621f99477a3611939f8fd2943aa1d51674b8702aa3226f8d
| Timestamp: 1780686677 | Timestamp [UTC]: 2026-06-05 19:11:17 | Age [y:d:h:m:s]: 00:003:05:35:30 |
| Block: 5442 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2444 | RingCT/type: yes/0 |
| Extra: 01d866b1f3d2487255621f99477a3611939f8fd2943aa1d51674b8702aa3226f8d020900000001e49593ff00 | ||
1 output(s) for total of 34.821120564765 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84b45ec06432c21bf7977757c3fa0ff0ebb90401cd0fb68c1147117d19bcbdfb | 34.821120564765 | 6881 of 0 | <83> |
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": 5502,
"vin": [ {
"gen": {
"height": 5442
}
}
],
"vout": [ {
"amount": 34821120564765,
"target": {
"tagged_key": {
"key": "84b45ec06432c21bf7977757c3fa0ff0ebb90401cd0fb68c1147117d19bcbdfb",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 216, 102, 177, 243, 210, 72, 114, 85, 98, 31, 153, 71, 122, 54, 17, 147, 159, 143, 210, 148, 58, 161, 213, 22, 116, 184, 112, 42, 163, 34, 111, 141, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}