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: c6352b33c3e4c527718b42add35a5deb117cb5e405efedf3677e66d924be0609
Tx prefix hash: 46cca7565652bb333d380eff39159d25d89e5493950f2125c6555829785e0f2b
Tx public key: 51a705b21c17547ac66f2d11898dc39c7f0aeec7cc9a91f71d4314f24964b3c6
| Timestamp: 1780821170 | Timestamp [UTC]: 2026-06-07 08:32:50 | Age [y:d:h:m:s]: 00:001:17:03:07 |
| Block: 7176 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 710 | RingCT/type: yes/0 |
| Extra: 0151a705b21c17547ac66f2d11898dc39c7f0aeec7cc9a91f71d4314f24964b3c6020900000001e49593ff00 | ||
1 output(s) for total of 34.706145318220 HMNY
| stealth address | amount | amount idx | tag |
| 00: 552dd6098c4674fb834b8489af2da56dbd1670fb3003deea467c78bc6a9a826b | 34.706145318220 | 8840 of 0 | <ce> |
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": 7236,
"vin": [ {
"gen": {
"height": 7176
}
}
],
"vout": [ {
"amount": 34706145318220,
"target": {
"tagged_key": {
"key": "552dd6098c4674fb834b8489af2da56dbd1670fb3003deea467c78bc6a9a826b",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 81, 167, 5, 178, 28, 23, 84, 122, 198, 111, 45, 17, 137, 141, 195, 156, 127, 10, 238, 199, 204, 154, 145, 247, 29, 67, 20, 242, 73, 100, 179, 198, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}