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: cf6a2405d64939892d6fc19f1bdbe67f3177625ffc4e57c88acd04358b86ff5a
Tx prefix hash: 6f9f481ad53488c8b2bf440a2e257e5240d2b99a8f4da8eff5a325082ebb99db
Tx public key: 431da256f0ad4820e63e251eb6ffe890fa698c2f5bcb37f2b69193a7441ca081
| Timestamp: 1780815482 | Timestamp [UTC]: 2026-06-07 06:58:02 | Age [y:d:h:m:s]: 00:001:19:42:34 |
| Block: 7061 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 835 | RingCT/type: yes/0 |
| Extra: 01431da256f0ad4820e63e251eb6ffe890fa698c2f5bcb37f2b69193a7441ca081020900000002e49593ff00 | ||
1 output(s) for total of 34.713758783103 HMNY
| stealth address | amount | amount idx | tag |
| 00: 40fcf145e7f0ecf7cd246c38f9bf678ec22ee9d67d266c8e92e53d008461e311 | 34.713758783103 | 8705 of 0 | <8f> |
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": 7121,
"vin": [ {
"gen": {
"height": 7061
}
}
],
"vout": [ {
"amount": 34713758783103,
"target": {
"tagged_key": {
"key": "40fcf145e7f0ecf7cd246c38f9bf678ec22ee9d67d266c8e92e53d008461e311",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 67, 29, 162, 86, 240, 173, 72, 32, 230, 62, 37, 30, 182, 255, 232, 144, 250, 105, 140, 47, 91, 203, 55, 242, 182, 145, 147, 167, 68, 28, 160, 129, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}