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: c274158d9bcfc5fd3e9b6ec192f59824e14210fbe8105d6be236d68dd9aec8fa
Tx prefix hash: cbecd5e627795f478f55e44e8ca00b073b750e3043fe932c830d94be6d5aaf70
Tx public key: 3fe538c902290bcb8745be20ede83fc407d7cb474d0ea1f4e231eaed9d24f0a5
| Timestamp: 1779846634 | Timestamp [UTC]: 2026-05-27 01:50:34 | Age [y:d:h:m:s]: 00:021:06:45:40 |
| Block: 2465 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6280 | RingCT/type: yes/0 |
| Extra: 013fe538c902290bcb8745be20ede83fc407d7cb474d0ea1f4e231eaed9d24f0a502090000000326697be300 | ||
1 output(s) for total of 35.019403646040 HMNY
| stealth address | amount | amount idx | tag |
| 00: 73e3b047c03825795df0347fd561d6ab5648aa24da0636f0f26d55f8d65d5f35 | 35.019403646040 | 2899 of 0 | <1e> |
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": 2525,
"vin": [ {
"gen": {
"height": 2465
}
}
],
"vout": [ {
"amount": 35019403646040,
"target": {
"tagged_key": {
"key": "73e3b047c03825795df0347fd561d6ab5648aa24da0636f0f26d55f8d65d5f35",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 63, 229, 56, 201, 2, 41, 11, 203, 135, 69, 190, 32, 237, 232, 63, 196, 7, 215, 203, 71, 77, 14, 161, 244, 226, 49, 234, 237, 157, 36, 240, 165, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}