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: fb392bd9e017907e71e9bc373ef8481bc37af83633ac4884abc162ed3292e79a
Tx prefix hash: ae95fce530a0970b370dd2bc5d7bc6fc849acfebc9f93e359fa38eb6fb4e38f4
Tx public key: d1f0496c0e0326823f37e5569fd9fbe78bbc0ec19cfbaa9e6688f8b5c0f0fe1b
| Timestamp: 1780976817 | Timestamp [UTC]: 2026-06-09 03:46:57 | Age [y:d:h:m:s]: 00:000:07:39:51 |
| Block: 7944 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 569 | RingCT/type: yes/0 |
| Extra: 01d1f0496c0e0326823f37e5569fd9fbe78bbc0ec19cfbaa9e6688f8b5c0f0fe1b020900000001e49593ff00 | ||
1 output(s) for total of 34.655343407231 HMNY
| stealth address | amount | amount idx | tag |
| 00: b5f5b48dc7e1099e0d2c94e4f74b023665f2f989cf09bb795912bc81238512bd | 34.655343407231 | 9852 of 0 | <5d> |
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": 8004,
"vin": [ {
"gen": {
"height": 7944
}
}
],
"vout": [ {
"amount": 34655343407231,
"target": {
"tagged_key": {
"key": "b5f5b48dc7e1099e0d2c94e4f74b023665f2f989cf09bb795912bc81238512bd",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 209, 240, 73, 108, 14, 3, 38, 130, 63, 55, 229, 86, 159, 217, 251, 231, 139, 188, 14, 193, 156, 251, 170, 158, 102, 136, 248, 181, 192, 240, 254, 27, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}