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: 0ab26a66e9044d3086959d913d4b228217fdb1102b8ff8b82c968872887abe8f
Tx prefix hash: 45097b28242a777dad7b6f19b86ebc0e1337f3cf15794a51ae8e0d4084dd6861
Tx public key: 317ae545e500f3a4aef1077f7db04e91322df83ef0bb685f5f2136afe87e5677
| Timestamp: 1780866854 | Timestamp [UTC]: 2026-06-07 21:14:14 | Age [y:d:h:m:s]: 00:001:03:32:33 |
| Block: 7676 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 210 | RingCT/type: yes/0 |
| Extra: 01317ae545e500f3a4aef1077f7db04e91322df83ef0bb685f5f2136afe87e5677020900000002e49593ff00 | ||
1 output(s) for total of 34.673062704786 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3efea01c3a6b3ca02b2b251c54b8ac71ae0c0c5e56d7b5494f20ff84b879fb3d | 34.673062704786 | 9492 of 0 | <7b> |
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": 7736,
"vin": [ {
"gen": {
"height": 7676
}
}
],
"vout": [ {
"amount": 34673062704786,
"target": {
"tagged_key": {
"key": "3efea01c3a6b3ca02b2b251c54b8ac71ae0c0c5e56d7b5494f20ff84b879fb3d",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 49, 122, 229, 69, 229, 0, 243, 164, 174, 241, 7, 127, 125, 176, 78, 145, 50, 45, 248, 62, 240, 187, 104, 95, 95, 33, 54, 175, 232, 126, 86, 119, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}