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: 3ee1ee61b6b2dfe6fe06c56a29fa32a3e40cbb149aaec872faba7135fc968ff6
Tx prefix hash: b534d68104af8b98f27f7fde589d716f2c6e0c62507a0dc55c82df4cf6d57b93
Tx public key: 5a071945147e460856671b89dd398bd9a2570b84378763ea1a973dc7e87c6de0
| Timestamp: 1779966540 | Timestamp [UTC]: 2026-05-28 11:09:00 | Age [y:d:h:m:s]: 00:019:22:06:06 |
| Block: 3811 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4934 | RingCT/type: yes/0 |
| Extra: 015a071945147e460856671b89dd398bd9a2570b84378763ea1a973dc7e87c6de002090000000226697be300 | ||
1 output(s) for total of 34.929613859091 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c9692ca29ac7dd68da06547e351fdf867c17d8d2722deca7633c5c24ff3dc52 | 34.929613859091 | 4640 of 0 | <ea> |
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": 3871,
"vin": [ {
"gen": {
"height": 3811
}
}
],
"vout": [ {
"amount": 34929613859091,
"target": {
"tagged_key": {
"key": "2c9692ca29ac7dd68da06547e351fdf867c17d8d2722deca7633c5c24ff3dc52",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 90, 7, 25, 69, 20, 126, 70, 8, 86, 103, 27, 137, 221, 57, 139, 217, 162, 87, 11, 132, 55, 135, 99, 234, 26, 151, 61, 199, 232, 124, 109, 224, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}