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: ccc44a1b20964467525ccdd3277a179f87411429629a54ded5a4bdc65fe60072
Tx prefix hash: dd0005daf74b6efb4a78ee7d586f1cd29281e85dff22efbef90bc93d8d96a61c
Tx public key: 024d12a74aa280c2109237af8db33ea06751e5e16f2d1b7ae443a9978ad10cf0
| Timestamp: 1781003752 | Timestamp [UTC]: 2026-06-09 11:15:52 | Age [y:d:h:m:s]: 00:007:23:04:20 |
| Block: 8496 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 249 | RingCT/type: yes/0 |
| Extra: 01024d12a74aa280c2109237af8db33ea06751e5e16f2d1b7ae443a9978ad10cf0020900000001e49593ff00 | ||
1 output(s) for total of 34.618875471901 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2f32a6d5974956f321661fe6195bdc23b7bbc0bb215475c17e120cab4defbf1 | 34.618875471901 | 10496 of 0 | <24> |
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": 8556,
"vin": [ {
"gen": {
"height": 8496
}
}
],
"vout": [ {
"amount": 34618875471901,
"target": {
"tagged_key": {
"key": "c2f32a6d5974956f321661fe6195bdc23b7bbc0bb215475c17e120cab4defbf1",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 2, 77, 18, 167, 74, 162, 128, 194, 16, 146, 55, 175, 141, 179, 62, 160, 103, 81, 229, 225, 111, 45, 27, 122, 228, 67, 169, 151, 138, 209, 12, 240, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}