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: f960535e957d127d5eefc283a54da1e047a1797f1aaa0f98716f6b0c1a3dece6
Tx prefix hash: 66bbee5892b0b48add9bc3a73dcdfa7e62085043f0e7aa49a9183dca261b6f3a
Tx public key: 05ac64d087d3b83cb30badb1638197530f3dc015228faef27c2c9c13e2922a87
| Timestamp: 1780075738 | Timestamp [UTC]: 2026-05-29 17:28:58 | Age [y:d:h:m:s]: 00:010:09:20:50 |
| Block: 4701 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3219 | RingCT/type: yes/0 |
| Extra: 0105ac64d087d3b83cb30badb1638197530f3dc015228faef27c2c9c13e2922a8702090000000526697be300 | ||
1 output(s) for total of 34.876190874911 HMNY
| stealth address | amount | amount idx | tag |
| 00: 72ca2c8cb935f2e6965129684635f8062c7ade59e61ac856ea5bfee02f40bfc0 | 34.876190874911 | 5905 of 0 | <d1> |
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": 4761,
"vin": [ {
"gen": {
"height": 4701
}
}
],
"vout": [ {
"amount": 34876190874911,
"target": {
"tagged_key": {
"key": "72ca2c8cb935f2e6965129684635f8062c7ade59e61ac856ea5bfee02f40bfc0",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 5, 172, 100, 208, 135, 211, 184, 60, 179, 11, 173, 177, 99, 129, 151, 83, 15, 61, 192, 21, 34, 143, 174, 242, 124, 44, 156, 19, 226, 146, 42, 135, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}