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: 38f43aeb3ccadd7522bc319e95e2d686fbeda7ae52063dbbafd934e650ff213d
Tx prefix hash: 5e504bb26af1647f9be3041741a812795b344f51c87882e2b7bc365fd60d6970
Tx public key: abe389101c45daefd3b44cdb66f23c9a8178e324a535fdb2fc71a500a7ee3576
| Timestamp: 1780998511 | Timestamp [UTC]: 2026-06-09 09:48:31 | Age [y:d:h:m:s]: 00:004:01:13:45 |
| Block: 8396 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 349 | RingCT/type: yes/0 |
| Extra: 01abe389101c45daefd3b44cdb66f23c9a8178e324a535fdb2fc71a500a7ee3576020900000001e49593ff00 | ||
1 output(s) for total of 34.625479134433 HMNY
| stealth address | amount | amount idx | tag |
| 00: d1bfd8c6ed676e5bb8119cf160f31be7a6cadc38b391dc1a9bbbcd3d3cf2717e | 34.625479134433 | 10378 of 0 | <03> |
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": 8456,
"vin": [ {
"gen": {
"height": 8396
}
}
],
"vout": [ {
"amount": 34625479134433,
"target": {
"tagged_key": {
"key": "d1bfd8c6ed676e5bb8119cf160f31be7a6cadc38b391dc1a9bbbcd3d3cf2717e",
"view_tag": "03"
}
}
}
],
"extra": [ 1, 171, 227, 137, 16, 28, 69, 218, 239, 211, 180, 76, 219, 102, 242, 60, 154, 129, 120, 227, 36, 165, 53, 253, 178, 252, 113, 165, 0, 167, 238, 53, 118, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}