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: d72843942a4376531e35d6c9411293830763035ca721219e9c7dc7a65fe3c447
Tx prefix hash: b052ee72850b15a403c89a334388fb0525b3aac173777df37d866df57af8cce5
Tx public key: 13df7597c4f65a2a30075e30b4cfe239c1cd53e7d73d6e7f9c5e423ae9e1a3fb
| Timestamp: 1779965012 | Timestamp [UTC]: 2026-05-28 10:43:32 | Age [y:d:h:m:s]: 00:011:17:07:26 |
| Block: 3798 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4168 | RingCT/type: yes/0 |
| Extra: 0113df7597c4f65a2a30075e30b4cfe239c1cd53e7d73d6e7f9c5e423ae9e1a3fb02090000000726697be300 | ||
1 output(s) for total of 34.930479969021 HMNY
| stealth address | amount | amount idx | tag |
| 00: 960077b46e7b1182624e7a44214504a61f4deb1a3c6aad5d279da7e41b1f5ebd | 34.930479969021 | 4618 of 0 | <cb> |
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": 3858,
"vin": [ {
"gen": {
"height": 3798
}
}
],
"vout": [ {
"amount": 34930479969021,
"target": {
"tagged_key": {
"key": "960077b46e7b1182624e7a44214504a61f4deb1a3c6aad5d279da7e41b1f5ebd",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 19, 223, 117, 151, 196, 246, 90, 42, 48, 7, 94, 48, 180, 207, 226, 57, 193, 205, 83, 231, 215, 61, 110, 127, 156, 94, 66, 58, 233, 225, 163, 251, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}