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: d8a176bc86ec99a4799e862a014fe892a084b3703975e963d976ebb991b0c94e
Tx prefix hash: 53fa566f579feb820f4aebaba84150e40a03cf238b7b36245bde0ec1edbf804b
Tx public key: b0ca7a08449dfa80244faef82a4e1a08caf8df078b21894dd05b7014ac3a4f39
| Timestamp: 1780859341 | Timestamp [UTC]: 2026-06-07 19:09:01 | Age [y:d:h:m:s]: 00:001:04:09:52 |
| Block: 7603 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 283 | RingCT/type: yes/0 |
| Extra: 01b0ca7a08449dfa80244faef82a4e1a08caf8df078b21894dd05b7014ac3a4f39020900000001e49593ff00 | ||
1 output(s) for total of 34.677890799674 HMNY
| stealth address | amount | amount idx | tag |
| 00: 589fc2855e4cee6d415f3c6f662b8f6a1d33b8a49a387433f5763517a50da7d6 | 34.677890799674 | 9393 of 0 | <4c> |
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": 7663,
"vin": [ {
"gen": {
"height": 7603
}
}
],
"vout": [ {
"amount": 34677890799674,
"target": {
"tagged_key": {
"key": "589fc2855e4cee6d415f3c6f662b8f6a1d33b8a49a387433f5763517a50da7d6",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 176, 202, 122, 8, 68, 157, 250, 128, 36, 79, 174, 248, 42, 78, 26, 8, 202, 248, 223, 7, 139, 33, 137, 77, 208, 91, 112, 20, 172, 58, 79, 57, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}