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: 76c1e7cf52b2bb6b0ec33716d5ebf479ecb2ee9b57c5be4973d5f9e7f2166ab5
Tx prefix hash: 2bb5240f1bf788c8b603fafe5222ba1a4e871e2339aeba3428c86fd6b7edf1e6
Tx public key: 03e1d20b12b8b2da296ee193eaab51fce04f4a803e3738a1b7b98c0ba903da82
| Timestamp: 1780109366 | Timestamp [UTC]: 2026-05-30 02:49:26 | Age [y:d:h:m:s]: 00:018:05:39:46 |
| Block: 4847 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3898 | RingCT/type: yes/0 |
| Extra: 0103e1d20b12b8b2da296ee193eaab51fce04f4a803e3738a1b7b98c0ba903da8202090000000226697be300 | ||
1 output(s) for total of 34.860660564595 HMNY
| stealth address | amount | amount idx | tag |
| 00: 22b1e54debb5c16d6eda5fd524540d78a646fe79f5a03bd689b0d2eef53c213e | 34.860660564595 | 6117 of 0 | <71> |
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": 4907,
"vin": [ {
"gen": {
"height": 4847
}
}
],
"vout": [ {
"amount": 34860660564595,
"target": {
"tagged_key": {
"key": "22b1e54debb5c16d6eda5fd524540d78a646fe79f5a03bd689b0d2eef53c213e",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 3, 225, 210, 11, 18, 184, 178, 218, 41, 110, 225, 147, 234, 171, 81, 252, 224, 79, 74, 128, 62, 55, 56, 161, 183, 185, 140, 11, 169, 3, 218, 130, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}