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: 49c3978c0a2b14dcfaa0651807cee1d2b3b4110475a059b6d521fa308f542c5b
Tx prefix hash: 8d3f7312e9ad3fa5eb1264da6ce0ccb8fbc7f41ab90bea079221fc7c048e62c0
Tx public key: a6b70fbd3a872c8f10467b078bfda70812821e009343c6b0b47708303bb679dc
| Timestamp: 1779975394 | Timestamp [UTC]: 2026-05-28 13:36:34 | Age [y:d:h:m:s]: 00:011:11:59:23 |
| Block: 3878 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4008 | RingCT/type: yes/0 |
| Extra: 01a6b70fbd3a872c8f10467b078bfda70812821e009343c6b0b47708303bb679dc02090000000326697be300 | ||
1 output(s) for total of 34.925150402306 HMNY
| stealth address | amount | amount idx | tag |
| 00: 176c0554a675e1159e0d88f093216d16af5aa2714d3ab47653eeb013bb7451b9 | 34.925150402306 | 4744 of 0 | <8d> |
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": 3938,
"vin": [ {
"gen": {
"height": 3878
}
}
],
"vout": [ {
"amount": 34925150402306,
"target": {
"tagged_key": {
"key": "176c0554a675e1159e0d88f093216d16af5aa2714d3ab47653eeb013bb7451b9",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 166, 183, 15, 189, 58, 135, 44, 143, 16, 70, 123, 7, 139, 253, 167, 8, 18, 130, 30, 0, 147, 67, 198, 176, 180, 119, 8, 48, 59, 182, 121, 220, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}