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: 24cf6c451649411ac5cc0269bd2fca8995f07c8cb80aeeed9d1048bc0ead39c4
Tx prefix hash: 1d9f7924c80f276af95f91e0739fd9b9e901adb801b42562b14d9a8b4d4509e6
Tx public key: acdd5179e5c9e734f4eec47a4c3801d52d46acda3df3dcad5ccf4bfc41fb1c99
| Timestamp: 1780744248 | Timestamp [UTC]: 2026-06-06 11:10:48 | Age [y:d:h:m:s]: 00:006:23:51:28 |
| Block: 6441 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2304 | RingCT/type: yes/0 |
| Extra: 01acdd5179e5c9e734f4eec47a4c3801d52d46acda3df3dcad5ccf4bfc41fb1c99020900000001e49593ff00 | ||
1 output(s) for total of 34.754834073428 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6a82ae0ec6f6e57a7196345f41fc8d8ea06c5c21dbf3191eef1bde44bfb87b6a | 34.754834073428 | 7934 of 0 | <39> |
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": 6501,
"vin": [ {
"gen": {
"height": 6441
}
}
],
"vout": [ {
"amount": 34754834073428,
"target": {
"tagged_key": {
"key": "6a82ae0ec6f6e57a7196345f41fc8d8ea06c5c21dbf3191eef1bde44bfb87b6a",
"view_tag": "39"
}
}
}
],
"extra": [ 1, 172, 221, 81, 121, 229, 201, 231, 52, 244, 238, 196, 122, 76, 56, 1, 213, 45, 70, 172, 218, 61, 243, 220, 173, 92, 207, 75, 252, 65, 251, 28, 153, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}