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: 8fe52d191ab0c6a5a33b60d52194c5773eafda2437322152fdbc16ad237d9e0b
Tx prefix hash: 038ee31853b50ff68108f9f529d300de6626b88bea500d5528a09261bca3cb0f
Tx public key: 86ac70186e130eaa76c987f194bd547a904736c67398873634c7cc90961fd6b3
| Timestamp: 1780383331 | Timestamp [UTC]: 2026-06-02 06:55:31 | Age [y:d:h:m:s]: 00:006:17:51:16 |
| Block: 5158 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2728 | RingCT/type: yes/0 |
| Extra: 0186ac70186e130eaa76c987f194bd547a904736c67398873634c7cc90961fd6b302090000000226697be300 | ||
1 output(s) for total of 34.839987841119 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2e686b8ed636e6c39c43a5963d577d46971c36a26a96e49da0cd8bbae7fbc6a | 34.839987841119 | 6537 of 0 | <22> |
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": 5218,
"vin": [ {
"gen": {
"height": 5158
}
}
],
"vout": [ {
"amount": 34839987841119,
"target": {
"tagged_key": {
"key": "c2e686b8ed636e6c39c43a5963d577d46971c36a26a96e49da0cd8bbae7fbc6a",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 134, 172, 112, 24, 110, 19, 14, 170, 118, 201, 135, 241, 148, 189, 84, 122, 144, 71, 54, 198, 115, 152, 135, 54, 52, 199, 204, 144, 150, 31, 214, 179, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}