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: e35f713257edebc31c620ad577b5378a5ca3e8e1f25ead174c99a716a38c7a23
Tx prefix hash: 7c776906a0cbd8b9b5d84c9358c12f521e3e606a7cb7fb17dbe7f01722788e94
Tx public key: c14ed076377fb4f2bfa4eb0ae5b42c2c8bd8b55e5339c0861c2b57afadba67e1
| Timestamp: 1779451050 | Timestamp [UTC]: 2026-05-22 11:57:30 | Age [y:d:h:m:s]: 00:017:14:43:06 |
| Block: 326 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7571 | RingCT/type: yes/0 |
| Extra: 01c14ed076377fb4f2bfa4eb0ae5b42c2c8bd8b55e5339c0861c2b57afadba67e10209000000084438f87f00 | ||
1 output(s) for total of 35.162568445961 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b70ddbd952c17381573d2010a10133a8349a65a7cca5a27fdaf38c16f184699 | 35.162568445961 | 322 of 0 | <82> |
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": 386,
"vin": [ {
"gen": {
"height": 326
}
}
],
"vout": [ {
"amount": 35162568445961,
"target": {
"tagged_key": {
"key": "1b70ddbd952c17381573d2010a10133a8349a65a7cca5a27fdaf38c16f184699",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 193, 78, 208, 118, 55, 127, 180, 242, 191, 164, 235, 10, 229, 180, 44, 44, 139, 216, 181, 94, 83, 57, 192, 134, 28, 43, 87, 175, 173, 186, 103, 225, 2, 9, 0, 0, 0, 8, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}