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: 7765c4565ff3e9a8e522bcfba308e35e97a471d610575a6cdce3f06123188ddf
Tx prefix hash: bef1e81fb6e499c4fa0bbb358b5584d704578145c8a44e118735c3f4e618d5b7
Tx public key: 57550a41ecfcedcb4e0e7bd4f2e879a55c0b4779b78a30fba0d02e57b23a1366
| Timestamp: 1780996336 | Timestamp [UTC]: 2026-06-09 09:12:16 | Age [y:d:h:m:s]: 00:007:23:51:41 |
| Block: 8343 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 402 | RingCT/type: yes/0 |
| Extra: 0157550a41ecfcedcb4e0e7bd4f2e879a55c0b4779b78a30fba0d02e57b23a1366020900000001e49593ff00 | ||
1 output(s) for total of 34.628979586293 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2173ea9abb983e5d897aa3802b1df11884b4214913f5ce7f5a93f687aa9249e9 | 34.628979586293 | 10319 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": 8403,
"vin": [ {
"gen": {
"height": 8343
}
}
],
"vout": [ {
"amount": 34628979586293,
"target": {
"tagged_key": {
"key": "2173ea9abb983e5d897aa3802b1df11884b4214913f5ce7f5a93f687aa9249e9",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 87, 85, 10, 65, 236, 252, 237, 203, 78, 14, 123, 212, 242, 232, 121, 165, 92, 11, 71, 121, 183, 138, 48, 251, 160, 208, 46, 87, 178, 58, 19, 102, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}