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: 1544724cde8d4bcca14c52d4360a5836e313f3446783c60fed7e706350635588
Tx prefix hash: e49a9139de2a8e96da9408ecd42e73efa8d1f4cb8b60e56f2843d47660de8bfb
Tx public key: 82eeb783fdf548a4b0d933898e2b5f46327251c07a676d3f7e433f632b500620
| Timestamp: 1780006010 | Timestamp [UTC]: 2026-05-28 22:06:50 | Age [y:d:h:m:s]: 00:011:01:12:03 |
| Block: 4075 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3811 | RingCT/type: yes/0 |
| Extra: 0182eeb783fdf548a4b0d933898e2b5f46327251c07a676d3f7e433f632b50062002090000000726697be300 | ||
1 output(s) for total of 34.914643410703 HMNY
| stealth address | amount | amount idx | tag |
| 00: 006118a277ed4133ce60de5061b46122c8b645bc5823297da9d7dca5eeb1b211 | 34.914643410703 | 5057 of 0 | <da> |
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": 4135,
"vin": [ {
"gen": {
"height": 4075
}
}
],
"vout": [ {
"amount": 34914643410703,
"target": {
"tagged_key": {
"key": "006118a277ed4133ce60de5061b46122c8b645bc5823297da9d7dca5eeb1b211",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 130, 238, 183, 131, 253, 245, 72, 164, 176, 217, 51, 137, 142, 43, 95, 70, 50, 114, 81, 192, 122, 103, 109, 63, 126, 67, 63, 99, 43, 80, 6, 32, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}