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: c4c9adf9d648ec78076c0a9b93dbb7ff5c59d74150d8455c8a86bc82dbe11e78
Tx prefix hash: 8b1279cae8ac29200530a923627b13f28cf6467f1e0d19be42796785fe797bc1
Tx public key: 0729b279e9392ec564a67a3d6663f6df5cba67280390028409f081b28b929625
| Timestamp: 1779515984 | Timestamp [UTC]: 2026-05-23 05:59:44 | Age [y:d:h:m:s]: 00:016:20:40:52 |
| Block: 679 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7217 | RingCT/type: yes/0 |
| Extra: 010729b279e9392ec564a67a3d6663f6df5cba67280390028409f081b28b929625020900000038ba6d17be00 | ||
1 output(s) for total of 35.141503242915 HMNY
| stealth address | amount | amount idx | tag |
| 00: be8cab62baff286a37d15cc94c32b6bfea603784950b2085402ebf844af9e1bf | 35.141503242915 | 750 of 0 | <4d> |
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": 739,
"vin": [ {
"gen": {
"height": 679
}
}
],
"vout": [ {
"amount": 35141503242915,
"target": {
"tagged_key": {
"key": "be8cab62baff286a37d15cc94c32b6bfea603784950b2085402ebf844af9e1bf",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 7, 41, 178, 121, 233, 57, 46, 197, 100, 166, 122, 61, 102, 99, 246, 223, 92, 186, 103, 40, 3, 144, 2, 132, 9, 240, 129, 178, 139, 146, 150, 37, 2, 9, 0, 0, 0, 56, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}