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: cab9df12e30a96e96c8f360eba71f00d1395b153caf6588b4d90779a11897513
Tx prefix hash: af0c8dec558ccc58bd0c9a9c7574a2fbaf3165fd75dc779235bad7c386df976d
Tx public key: 4a4bb5de3ae112f32cf1497053cf32adb4e69f91b0f7adedfe7377bb10bb4c54
| Timestamp: 1780839936 | Timestamp [UTC]: 2026-06-07 13:45:36 | Age [y:d:h:m:s]: 00:001:11:50:21 |
| Block: 7454 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 432 | RingCT/type: yes/0 |
| Extra: 014a4bb5de3ae112f32cf1497053cf32adb4e69f91b0f7adedfe7377bb10bb4c54020900000002e49593ff00 | ||
1 output(s) for total of 34.687747490932 HMNY
| stealth address | amount | amount idx | tag |
| 00: 35b9ee9e76bd1232f983f298207429e68b23f992b29cc5ab79f920b92a3cf7cd | 34.687747490932 | 9180 of 0 | <58> |
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": 7514,
"vin": [ {
"gen": {
"height": 7454
}
}
],
"vout": [ {
"amount": 34687747490932,
"target": {
"tagged_key": {
"key": "35b9ee9e76bd1232f983f298207429e68b23f992b29cc5ab79f920b92a3cf7cd",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 74, 75, 181, 222, 58, 225, 18, 243, 44, 241, 73, 112, 83, 207, 50, 173, 180, 230, 159, 145, 176, 247, 173, 237, 254, 115, 119, 187, 16, 187, 76, 84, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}