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: 6900388e6e7872e81c29df0f3ebdfaafc14a62ff9c0fc930bfc2e0e6acafea21
Tx prefix hash: 2d864d48dc991eee06520f6555a1b4c8babf2876fe4266670b85fbc51b95a70b
Tx public key: 41b13da14a9c258f59c54855a2a5789f8095e5fbf6b5af29f1439ce53d786d63
| Timestamp: 1779958525 | Timestamp [UTC]: 2026-05-28 08:55:25 | Age [y:d:h:m:s]: 00:012:08:13:38 |
| Block: 3725 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5010 | RingCT/type: yes/0 |
| Extra: 0141b13da14a9c258f59c54855a2a5789f8095e5fbf6b5af29f1439ce53d786d6302090000000426697be300 | ||
1 output(s) for total of 34.935343908305 HMNY
| stealth address | amount | amount idx | tag |
| 00: f636321b52c4d852bec632960cba9c9b163df58010f06ee048394d44369b86d7 | 34.935343908305 | 4511 of 0 | <89> |
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": 3785,
"vin": [ {
"gen": {
"height": 3725
}
}
],
"vout": [ {
"amount": 34935343908305,
"target": {
"tagged_key": {
"key": "f636321b52c4d852bec632960cba9c9b163df58010f06ee048394d44369b86d7",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 65, 177, 61, 161, 74, 156, 37, 143, 89, 197, 72, 85, 162, 165, 120, 159, 128, 149, 229, 251, 246, 181, 175, 41, 241, 67, 156, 229, 61, 120, 109, 99, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}