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: 1c346e7f85a320350816165943d0de3d57373e25c84c8f53a27ee54a19540afb
Tx prefix hash: 16607e62c5431c561bb39089918aedd488035b61836a3abd6f02c9c4c3e9cc53
Tx public key: bc15bd817e1de0684d556d452cd6ab006d791c6e5ff3e8f23de9df624db9fb08
| Timestamp: 1780868570 | Timestamp [UTC]: 2026-06-07 21:42:50 | Age [y:d:h:m:s]: 00:000:23:29:17 |
| Block: 7688 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 198 | RingCT/type: yes/0 |
| Extra: 01bc15bd817e1de0684d556d452cd6ab006d791c6e5ff3e8f23de9df624db9fb08020900000001e49593ff00 | ||
1 output(s) for total of 34.672269109686 HMNY
| stealth address | amount | amount idx | tag |
| 00: c49395ddbe0acce669e0e3746f46e87d0fd9eba88c222a57c8c61c17bbe86113 | 34.672269109686 | 9510 of 0 | <5f> |
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": 7748,
"vin": [ {
"gen": {
"height": 7688
}
}
],
"vout": [ {
"amount": 34672269109686,
"target": {
"tagged_key": {
"key": "c49395ddbe0acce669e0e3746f46e87d0fd9eba88c222a57c8c61c17bbe86113",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 188, 21, 189, 129, 126, 29, 224, 104, 77, 85, 109, 69, 44, 214, 171, 0, 109, 121, 28, 110, 95, 243, 232, 242, 61, 233, 223, 98, 77, 185, 251, 8, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}