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: ecabfd4e81b79126b8acef9bc89872b54202d7e48548bc6a909c5e687c5fe2d1
Tx prefix hash: efbd418128648b1914048dd6dcff0e01c6a5e8223bbd7ecc5263e86dd091bd34
Tx public key: 4e616c80d9934dd1e9992043e0f1f79c39794e805c96f1140e7841798b9cb9f3
| Timestamp: 1779435633 | Timestamp [UTC]: 2026-05-22 07:40:33 | Age [y:d:h:m:s]: 00:024:00:39:02 |
| Block: 123 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8622 | RingCT/type: yes/0 |
| Extra: 014e616c80d9934dd1e9992043e0f1f79c39794e805c96f1140e7841798b9cb9f3020900000001a662ed0300 | ||
1 output(s) for total of 35.176185752233 HMNY
| stealth address | amount | amount idx | tag |
| 00: 376139ddb9eb631fdd644cbae8917fed8188772fff6777836e44046a89297d48 | 35.176185752233 | 119 of 0 | <f3> |
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": 183,
"vin": [ {
"gen": {
"height": 123
}
}
],
"vout": [ {
"amount": 35176185752233,
"target": {
"tagged_key": {
"key": "376139ddb9eb631fdd644cbae8917fed8188772fff6777836e44046a89297d48",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 78, 97, 108, 128, 217, 147, 77, 209, 233, 153, 32, 67, 224, 241, 247, 156, 57, 121, 78, 128, 92, 150, 241, 20, 14, 120, 65, 121, 139, 156, 185, 243, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}