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: 92248aa2e9e880ce3c358241eedf856278c44c43b5dd44cc107ef548a74a1c98
Tx prefix hash: 9c2ea1153f7c059b6b5d2c0dd2e20fc6513378a66d5b582946ca6b7c5a77b831
Tx public key: 1c3325db98cbb4f0004900f7d52587b3f4a0fe384a095c58ebd04ae355a05de4
| Timestamp: 1779730935 | Timestamp [UTC]: 2026-05-25 17:42:15 | Age [y:d:h:m:s]: 00:014:08:58:21 |
| Block: 1882 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6015 | RingCT/type: yes/0 |
| Extra: 011c3325db98cbb4f0004900f7d52587b3f4a0fe384a095c58ebd04ae355a05de4020900000001ba6d17be00 | ||
1 output(s) for total of 35.058366367550 HMNY
| stealth address | amount | amount idx | tag |
| 00: a519092f9c87bc7c7820939196a4b38e825b39ddcffb53995acdb11197e308c5 | 35.058366367550 | 2099 of 0 | <a2> |
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": 1942,
"vin": [ {
"gen": {
"height": 1882
}
}
],
"vout": [ {
"amount": 35058366367550,
"target": {
"tagged_key": {
"key": "a519092f9c87bc7c7820939196a4b38e825b39ddcffb53995acdb11197e308c5",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 28, 51, 37, 219, 152, 203, 180, 240, 0, 73, 0, 247, 213, 37, 135, 179, 244, 160, 254, 56, 74, 9, 92, 88, 235, 208, 74, 227, 85, 160, 93, 228, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}