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: e04da5f874f2f60c88b2563b8259d24240198afd47855ee4a89325c5f279c73b
Tx prefix hash: 818417898e2d0cb2daba9921b989994b4782bd842dfb9933b6c2f7718de7f20c
Tx public key: d1c0899d001d797c93c9d5dc5c77f5ccc3781a2583eb7cf8b18d0eaec3f1cbb2
| Timestamp: 1779434717 | Timestamp [UTC]: 2026-05-22 07:25:17 | Age [y:d:h:m:s]: 00:017:20:13:33 |
| Block: 100 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7850 | RingCT/type: yes/0 |
| Extra: 01d1c0899d001d797c93c9d5dc5c77f5ccc3781a2583eb7cf8b18d0eaec3f1cbb2020900000001a662ed0300 | ||
1 output(s) for total of 35.177728932299 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a3cbfe77baf4e058a754ca6a0cbd4aed2779ed63e718452f9cee98b4cba8ac0 | 35.177728932299 | 96 of 0 | <45> |
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": 160,
"vin": [ {
"gen": {
"height": 100
}
}
],
"vout": [ {
"amount": 35177728932299,
"target": {
"tagged_key": {
"key": "5a3cbfe77baf4e058a754ca6a0cbd4aed2779ed63e718452f9cee98b4cba8ac0",
"view_tag": "45"
}
}
}
],
"extra": [ 1, 209, 192, 137, 157, 0, 29, 121, 124, 147, 201, 213, 220, 92, 119, 245, 204, 195, 120, 26, 37, 131, 235, 124, 248, 177, 141, 14, 174, 195, 241, 203, 178, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}