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: 273a67f72e89d9b6694d5ed451bd67007aab0fb75be196b4f40eb4728fc9bc09
Tx prefix hash: 2e3f4cdac5b739c82a238cb0ebd26d31134088a58d92f9015bda4665102abc5a
Tx public key: cb0be129beea82cd87e410ebcc1bc309f113b522dd6ee71b13b72997da7c509c
| Timestamp: 1780977028 | Timestamp [UTC]: 2026-06-09 03:50:28 | Age [y:d:h:m:s]: 00:000:04:03:46 |
| Block: 7950 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 296 | RingCT/type: yes/0 |
| Extra: 01cb0be129beea82cd87e410ebcc1bc309f113b522dd6ee71b13b72997da7c509c020900000003e49593ff00 | ||
1 output(s) for total of 34.654946810191 HMNY
| stealth address | amount | amount idx | tag |
| 00: b637386f0da76abf7dd4e88c38964466cf480adb252bac3e765ad98fa0e54676 | 34.654946810191 | 9862 of 0 | <b7> |
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": 8010,
"vin": [ {
"gen": {
"height": 7950
}
}
],
"vout": [ {
"amount": 34654946810191,
"target": {
"tagged_key": {
"key": "b637386f0da76abf7dd4e88c38964466cf480adb252bac3e765ad98fa0e54676",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 203, 11, 225, 41, 190, 234, 130, 205, 135, 228, 16, 235, 204, 27, 195, 9, 241, 19, 181, 34, 221, 110, 231, 27, 19, 183, 41, 151, 218, 124, 80, 156, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}