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: 50a2658d17f02bddb9fa646d59194fef8d054fcd9539d305cc8d487e6e00e8ee
Tx prefix hash: 26f948ec322fad0ed2936128e3843160171d1bbe59800e9ef0e0a19065d15f73
Tx public key: b6d1376858fc25aaf820c8db6fdb4238b27dee0570f16f9a2d3da8975fd77cd3
| Timestamp: 1780075534 | Timestamp [UTC]: 2026-05-29 17:25:34 | Age [y:d:h:m:s]: 00:014:17:36:42 |
| Block: 4697 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4048 | RingCT/type: yes/0 |
| Extra: 01b6d1376858fc25aaf820c8db6fdb4238b27dee0570f16f9a2d3da8975fd77cd302090000000326697be300 | ||
1 output(s) for total of 34.870635715987 HMNY
| stealth address | amount | amount idx | tag |
| 00: 68883b42b8e8163d597beeec035edaf31b56b6cd08213e9861ef8e4db2c9b660 | 34.870635715987 | 5901 of 0 | <73> |
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": 4757,
"vin": [ {
"gen": {
"height": 4697
}
}
],
"vout": [ {
"amount": 34870635715987,
"target": {
"tagged_key": {
"key": "68883b42b8e8163d597beeec035edaf31b56b6cd08213e9861ef8e4db2c9b660",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 182, 209, 55, 104, 88, 252, 37, 170, 248, 32, 200, 219, 111, 219, 66, 56, 178, 125, 238, 5, 112, 241, 111, 154, 45, 61, 168, 151, 95, 215, 124, 211, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}