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: 0a3ff4b563f274a05e3d32dcb6e1504bdb45bcdafbe1745f1dd917ac2711d7d2
Tx prefix hash: 8e805bd4743a994a10e0fac1a47f7938fed30b2e5df07b3b062b28a45d0f9bce
Tx public key: be6e21f0c6a63a0ce24fd0dc31c0651a9c960a1ee84f4b821ed0d9d5f2a71b61
| Timestamp: 1779461197 | Timestamp [UTC]: 2026-05-22 14:46:37 | Age [y:d:h:m:s]: 00:017:11:53:59 |
| Block: 440 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7456 | RingCT/type: yes/0 |
| Extra: 01be6e21f0c6a63a0ce24fd0dc31c0651a9c960a1ee84f4b821ed0d9d5f2a71b6102090000000293369e7d00 | ||
1 output(s) for total of 35.154923600279 HMNY
| stealth address | amount | amount idx | tag |
| 00: 118da4bcd28b23be65032b37ec4f25c74e9caa8fe831e62a5f509e6c84d74185 | 35.154923600279 | 444 of 0 | <01> |
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": 500,
"vin": [ {
"gen": {
"height": 440
}
}
],
"vout": [ {
"amount": 35154923600279,
"target": {
"tagged_key": {
"key": "118da4bcd28b23be65032b37ec4f25c74e9caa8fe831e62a5f509e6c84d74185",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 190, 110, 33, 240, 198, 166, 58, 12, 226, 79, 208, 220, 49, 192, 101, 26, 156, 150, 10, 30, 232, 79, 75, 130, 30, 208, 217, 213, 242, 167, 27, 97, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}