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: c99ef53741cf62e19d1770de064cb27d497b67c26c51c8f60212114e23aa72df
Tx prefix hash: 4455d34429cfdcd4b837323ed530b512d2e56b123580714d516fba5b77e010a0
Tx public key: d8f3e0f75d0be83d29064f28ac87caf3ed823098a46ab341b123c3dbcbc59864
| Timestamp: 1779875619 | Timestamp [UTC]: 2026-05-27 09:53:39 | Age [y:d:h:m:s]: 00:012:16:56:09 |
| Block: 2882 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5038 | RingCT/type: yes/0 |
| Extra: 01d8f3e0f75d0be83d29064f28ac87caf3ed823098a46ab341b123c3dbcbc5986402090000000226697be300 | ||
1 output(s) for total of 34.991561507013 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d4176d8cd3051cc98a9c9f5c7853922e39ffe044d156c97d6cd1f3ab76eb06b | 34.991561507013 | 3412 of 0 | <98> |
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": 2942,
"vin": [ {
"gen": {
"height": 2882
}
}
],
"vout": [ {
"amount": 34991561507013,
"target": {
"tagged_key": {
"key": "2d4176d8cd3051cc98a9c9f5c7853922e39ffe044d156c97d6cd1f3ab76eb06b",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 216, 243, 224, 247, 93, 11, 232, 61, 41, 6, 79, 40, 172, 135, 202, 243, 237, 130, 48, 152, 164, 106, 179, 65, 177, 35, 195, 219, 203, 197, 152, 100, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}