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: 5756937085bf59c66e38fb72868bcb313e4ecf71f0c8078c1f083972b7cbb04b
Tx prefix hash: d7fea9b284f8dab3dc4da83555df8513317791d427be910bb2dda28e10135496
Tx public key: f5ff11a6a6ccfb2e0091438d959fde9bae9a56dbb9f0dfab67b2ad82f6db43b4
| Timestamp: 1780692295 | Timestamp [UTC]: 2026-06-05 20:44:55 | Age [y:d:h:m:s]: 00:003:04:51:02 |
| Block: 5785 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2101 | RingCT/type: yes/0 |
| Extra: 01f5ff11a6a6ccfb2e0091438d959fde9bae9a56dbb9f0dfab67b2ad82f6db43b4020900000001e49593ff00 | ||
1 output(s) for total of 34.798347299499 HMNY
| stealth address | amount | amount idx | tag |
| 00: ed5da20f5eb562e9810b870a61b0c178481805d5b6714df9cbd27493ce3fc6c1 | 34.798347299499 | 7240 of 0 | <3f> |
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": 5845,
"vin": [ {
"gen": {
"height": 5785
}
}
],
"vout": [ {
"amount": 34798347299499,
"target": {
"tagged_key": {
"key": "ed5da20f5eb562e9810b870a61b0c178481805d5b6714df9cbd27493ce3fc6c1",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 245, 255, 17, 166, 166, 204, 251, 46, 0, 145, 67, 141, 149, 159, 222, 155, 174, 154, 86, 219, 185, 240, 223, 171, 103, 178, 173, 130, 246, 219, 67, 180, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}