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: ef6d97d73a768a189a95b8cdbe626f515b877b23d748795c5d15e36d4c622c33
Tx prefix hash: 3b0ed01d5e169a99f5efe94cc85d1bb4e812a2494c254c93780b572422212352
Tx public key: f0493cc9b452dd5b3f22598f6e7bfe6eb8d456ade5f5fd7de33ff66f4acf9aca
| Timestamp: 1781012936 | Timestamp [UTC]: 2026-06-09 13:48:56 | Age [y:d:h:m:s]: 00:006:07:14:45 |
| Block: 8602 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 143 | RingCT/type: yes/0 |
| Extra: 01f0493cc9b452dd5b3f22598f6e7bfe6eb8d456ade5f5fd7de33ff66f4acf9aca020900000001e49593ff00 | ||
1 output(s) for total of 34.611876964657 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7d6e17d3eb3e5449745cd1f9c78719b41b3b06d11ab8a7a91b3383dccd3858f9 | 34.611876964657 | 10630 of 0 | <a3> |
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": 8662,
"vin": [ {
"gen": {
"height": 8602
}
}
],
"vout": [ {
"amount": 34611876964657,
"target": {
"tagged_key": {
"key": "7d6e17d3eb3e5449745cd1f9c78719b41b3b06d11ab8a7a91b3383dccd3858f9",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 240, 73, 60, 201, 180, 82, 221, 91, 63, 34, 89, 143, 110, 123, 254, 110, 184, 212, 86, 173, 229, 245, 253, 125, 227, 63, 246, 111, 74, 207, 154, 202, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}