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: 47e41e18e20a017b1f15668c8ed206839c75b608747619a2c294e9481c56c12f
Tx prefix hash: 349946dad588d72705e9c924d4a987dac3d062241e78b695c111a32c8d81330a
Tx public key: 18c3c0811ce6e0ef450547789e6777f35bcd6629c69e15d02d9777fb6c7b0b46
| Timestamp: 1779616410 | Timestamp [UTC]: 2026-05-24 09:53:30 | Age [y:d:h:m:s]: 00:015:16:56:18 |
| Block: 757 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7142 | RingCT/type: yes/0 |
| Extra: 0118c3c0811ce6e0ef450547789e6777f35bcd6629c69e15d02d9777fb6c7b0b46 | ||
1 output(s) for total of 35.133674300176 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3b4b8324055d08b479d18790645c7953470025a5790ac6ed6088d60287ffa5f | 35.133674300176 | 889 of 0 | <15> |
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": 817,
"vin": [ {
"gen": {
"height": 757
}
}
],
"vout": [ {
"amount": 35133674300176,
"target": {
"tagged_key": {
"key": "c3b4b8324055d08b479d18790645c7953470025a5790ac6ed6088d60287ffa5f",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 24, 195, 192, 129, 28, 230, 224, 239, 69, 5, 71, 120, 158, 103, 119, 243, 91, 205, 102, 41, 198, 158, 21, 208, 45, 151, 119, 251, 108, 123, 11, 70
],
"rct_signatures": {
"type": 0
}
}