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: d688515dad2cc88beee3bea160defb5fbdbaed23c22de18daef3a293736c6078
Tx prefix hash: 67153c5c4d20f2e8ea45c5f20d0c49da0088d190484aad69c131854a9b9db65b
Tx public key: 8b50918973781d1ecf7a152ef1d2b9c27213cd1e209c0ee41a5e4cf398c16fa2
| Timestamp: 1780055099 | Timestamp [UTC]: 2026-05-29 11:44:59 | Age [y:d:h:m:s]: 00:010:11:33:54 |
| Block: 4443 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3443 | RingCT/type: yes/0 |
| Extra: 018b50918973781d1ecf7a152ef1d2b9c27213cd1e209c0ee41a5e4cf398c16fa202090000000326697be300 | ||
1 output(s) for total of 34.887533481649 HMNY
| stealth address | amount | amount idx | tag |
| 00: a939947b778bd0287561f0431e03a307941cb7f84b2e26092b8ac916cc36ee28 | 34.887533481649 | 5561 of 0 | <72> |
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": 4503,
"vin": [ {
"gen": {
"height": 4443
}
}
],
"vout": [ {
"amount": 34887533481649,
"target": {
"tagged_key": {
"key": "a939947b778bd0287561f0431e03a307941cb7f84b2e26092b8ac916cc36ee28",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 139, 80, 145, 137, 115, 120, 29, 30, 207, 122, 21, 46, 241, 210, 185, 194, 114, 19, 205, 30, 32, 156, 14, 228, 26, 94, 76, 243, 152, 193, 111, 162, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}