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: 18db8d5491c6c5e2a30d1001372ee950b47e9882a0720f5ab0a8759af42779cf
Tx prefix hash: 80ad5529324cd975f320d44175950499ebca4843ad53a42127e9862882e8ad13
Tx public key: 10cc15816c087fe023ffad91f0f12879681a6ea51adb371de9cb3eece09e8fb0
| Timestamp: 1780799328 | Timestamp [UTC]: 2026-06-07 02:28:48 | Age [y:d:h:m:s]: 00:001:23:07:09 |
| Block: 6811 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1075 | RingCT/type: yes/0 |
| Extra: 0110cc15816c087fe023ffad91f0f12879681a6ea51adb371de9cb3eece09e8fb0020900000001e49593ff00 | ||
1 output(s) for total of 34.730315556110 HMNY
| stealth address | amount | amount idx | tag |
| 00: a90fa54d7a8db8e55638362deb95934e2b03390807753db895dc429536828cc6 | 34.730315556110 | 8409 of 0 | <81> |
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": 6871,
"vin": [ {
"gen": {
"height": 6811
}
}
],
"vout": [ {
"amount": 34730315556110,
"target": {
"tagged_key": {
"key": "a90fa54d7a8db8e55638362deb95934e2b03390807753db895dc429536828cc6",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 16, 204, 21, 129, 108, 8, 127, 224, 35, 255, 173, 145, 240, 241, 40, 121, 104, 26, 110, 165, 26, 219, 55, 29, 233, 203, 62, 236, 224, 158, 143, 176, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}