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: 49e819bd4fc06428849c63f2f0154802bedc358791aa35169b9f94e16145fa1e
Tx prefix hash: 0ed7420be5cf6e6f581ec7a772266ab2a26166f393b89cc59bf6fe354d0aba51
Tx public key: d9324af17a5288ed09c716068282f1eb6bbf966d3446f104e05bb0a81169bd8e
| Timestamp: 1779479528 | Timestamp [UTC]: 2026-05-22 19:52:08 | Age [y:d:h:m:s]: 00:017:06:57:40 |
| Block: 636 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7284 | RingCT/type: yes/0 |
| Extra: 01d9324af17a5288ed09c716068282f1eb6bbf966d3446f104e05bb0a81169bd8e02090000000593369e7d00 | ||
1 output(s) for total of 35.145089715699 HMNY
| stealth address | amount | amount idx | tag |
| 00: f683715559876ec5528ff4577b765a21e930d86288b7ba17b6e112a908654974 | 35.145089715699 | 670 of 0 | <2c> |
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": 696,
"vin": [ {
"gen": {
"height": 636
}
}
],
"vout": [ {
"amount": 35145089715699,
"target": {
"tagged_key": {
"key": "f683715559876ec5528ff4577b765a21e930d86288b7ba17b6e112a908654974",
"view_tag": "2c"
}
}
}
],
"extra": [ 1, 217, 50, 74, 241, 122, 82, 136, 237, 9, 199, 22, 6, 130, 130, 241, 235, 107, 191, 150, 109, 52, 70, 241, 4, 224, 91, 176, 168, 17, 105, 189, 142, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}