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: a787de2a4653fa6a93f83f3761e9600aaebe359e63f06e783b64e268deb24db1
Tx prefix hash: d38df7f8b73270d31b646cba92d5d3fd2cba223e6aa12d76d39803d648e54d79
Tx public key: fcc6c3f48c947f1347591e5344b400b22c93477c13c25be55d54eba83e294466
| Timestamp: 1779884028 | Timestamp [UTC]: 2026-05-27 12:13:48 | Age [y:d:h:m:s]: 00:016:22:48:28 |
| Block: 2988 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5757 | RingCT/type: yes/0 |
| Extra: 01fcc6c3f48c947f1347591e5344b400b22c93477c13c25be55d54eba83e29446602090000000126697be300 | ||
1 output(s) for total of 34.984487658041 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3169c874860a30bc1da032c3c6d8b3b2996a379d8f757192a2b212217a78a985 | 34.984487658041 | 3546 of 0 | <54> |
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": 3048,
"vin": [ {
"gen": {
"height": 2988
}
}
],
"vout": [ {
"amount": 34984487658041,
"target": {
"tagged_key": {
"key": "3169c874860a30bc1da032c3c6d8b3b2996a379d8f757192a2b212217a78a985",
"view_tag": "54"
}
}
}
],
"extra": [ 1, 252, 198, 195, 244, 140, 148, 127, 19, 71, 89, 30, 83, 68, 180, 0, 178, 44, 147, 71, 124, 19, 194, 91, 229, 93, 84, 235, 168, 62, 41, 68, 102, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}