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: c97b1e57fa2b9260de9a833ff1c08e6c302afd027d7c94cf7b2a94e2fe0201b6
Tx prefix hash: 882a0905a3822033d36c878283667f090aec119f79cfb28144b8e8c1f39981b6
Tx public key: c573ed46d04e193d1a93da05aec735a26c112bfc0d34afa235cb5dfac2ef17d5
| Timestamp: 1781007314 | Timestamp [UTC]: 2026-06-09 12:15:14 | Age [y:d:h:m:s]: 00:007:20:07:05 |
| Block: 8566 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 179 | RingCT/type: yes/0 |
| Extra: 01c573ed46d04e193d1a93da05aec735a26c112bfc0d34afa235cb5dfac2ef17d5020900000004e49593ff00 | ||
1 output(s) for total of 34.614253657503 HMNY
| stealth address | amount | amount idx | tag |
| 00: ea9c6a092e406db8b77830428e96daaab800158b340a60bfb518807b326b93ae | 34.614253657503 | 10578 of 0 | <cf> |
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": 8626,
"vin": [ {
"gen": {
"height": 8566
}
}
],
"vout": [ {
"amount": 34614253657503,
"target": {
"tagged_key": {
"key": "ea9c6a092e406db8b77830428e96daaab800158b340a60bfb518807b326b93ae",
"view_tag": "cf"
}
}
}
],
"extra": [ 1, 197, 115, 237, 70, 208, 78, 25, 61, 26, 147, 218, 5, 174, 199, 53, 162, 108, 17, 43, 252, 13, 52, 175, 162, 53, 203, 93, 250, 194, 239, 23, 213, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}