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: bcf916457e6be97b3a52fffa487892a0200f30d4f33ce8c390019cfded11978a
Tx prefix hash: cc23e2775e04d795f97577627d46919e5f681035c0d2871b9ba1dec8868872e7
Tx public key: 7217340da22cad85baec50e25fd66cdb23f7c8fc5bea152263c8d6501e9565fb
| Timestamp: 1779871561 | Timestamp [UTC]: 2026-05-27 08:46:01 | Age [y:d:h:m:s]: 00:012:16:00:46 |
| Block: 2816 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5070 | RingCT/type: yes/0 |
| Extra: 017217340da22cad85baec50e25fd66cdb23f7c8fc5bea152263c8d6501e9565fb02090000000126697be300 | ||
1 output(s) for total of 34.995966701544 HMNY
| stealth address | amount | amount idx | tag |
| 00: f449d996d8bf28d983fe161c11f79a91f19c59b3ab2e1f5dddf46051bee135b2 | 34.995966701544 | 3332 of 0 | <68> |
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": 2876,
"vin": [ {
"gen": {
"height": 2816
}
}
],
"vout": [ {
"amount": 34995966701544,
"target": {
"tagged_key": {
"key": "f449d996d8bf28d983fe161c11f79a91f19c59b3ab2e1f5dddf46051bee135b2",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 114, 23, 52, 13, 162, 44, 173, 133, 186, 236, 80, 226, 95, 214, 108, 219, 35, 247, 200, 252, 91, 234, 21, 34, 99, 200, 214, 80, 30, 149, 101, 251, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}