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: a84c23825eccbfe669f8b7b75899dd9f105209db7528ce7de0e90f0aa1a8fd86
Tx prefix hash: 386c7b28b729a5ec726fa88d8705353dbe0a857ae5a1d44b2db8f1d6bd71b904
Tx public key: c01f51a30294e3e325f76c6db35947dc5c51b20ccc47020fd918c684f5b3633e
| Timestamp: 1779909365 | Timestamp [UTC]: 2026-05-27 19:16:05 | Age [y:d:h:m:s]: 00:012:09:16:57 |
| Block: 3225 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4802 | RingCT/type: yes/0 |
| Extra: 01c01f51a30294e3e325f76c6db35947dc5c51b20ccc47020fd918c684f5b3633e02090000000126697be300 | ||
1 output(s) for total of 34.968676772136 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7258746597e67fc9ec5e22e0d054f383d72c3a2aa5519239bc2676295795d759 | 34.968676772136 | 3867 of 0 | <33> |
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": 3285,
"vin": [ {
"gen": {
"height": 3225
}
}
],
"vout": [ {
"amount": 34968676772136,
"target": {
"tagged_key": {
"key": "7258746597e67fc9ec5e22e0d054f383d72c3a2aa5519239bc2676295795d759",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 192, 31, 81, 163, 2, 148, 227, 227, 37, 247, 108, 109, 179, 89, 71, 220, 92, 81, 178, 12, 204, 71, 2, 15, 217, 24, 198, 132, 245, 179, 99, 62, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}