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: d7e96dc81ad7d9108e9ee5cd7c0b27a8ea54177a900583c2809a3e04b39c9a2e
Tx prefix hash: 2d23a2d229341b16309630ef6d7925def9a3121a9b7e3fa3a7d492d7ad7d457c
Tx public key: 62330ea1f32ffe5cd5a34be0c09b0e2a9f659d4b8979e7ca7b40e811395a9226
| Timestamp: 1781017341 | Timestamp [UTC]: 2026-06-09 15:02:21 | Age [y:d:h:m:s]: 00:006:04:19:48 |
| Block: 8647 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 98 | RingCT/type: yes/0 |
| Extra: 0162330ea1f32ffe5cd5a34be0c09b0e2a9f659d4b8979e7ca7b40e811395a9226020900000001e49593ff00 | ||
1 output(s) for total of 34.608906328082 HMNY
| stealth address | amount | amount idx | tag |
| 00: ea390400b6e14e33240a74466139b6ddd60cfc11802b20ce2d55c88fc642d97e | 34.608906328082 | 10691 of 0 | <95> |
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": 8707,
"vin": [ {
"gen": {
"height": 8647
}
}
],
"vout": [ {
"amount": 34608906328082,
"target": {
"tagged_key": {
"key": "ea390400b6e14e33240a74466139b6ddd60cfc11802b20ce2d55c88fc642d97e",
"view_tag": "95"
}
}
}
],
"extra": [ 1, 98, 51, 14, 161, 243, 47, 254, 92, 213, 163, 75, 224, 192, 155, 14, 42, 159, 101, 157, 75, 137, 121, 231, 202, 123, 64, 232, 17, 57, 90, 146, 38, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}