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: ca60561e5d67282e8f015800e6ad2d59fdb1ead3d619cc29145bf761ff7dcb10
Tx prefix hash: f3948f16ef07a48238828d9d0d7af66b8883e3c311d3e4ebdaf23415b4a0ab29
Tx public key: 8801eb4e862c84641fd7e9b3993f8290b0637bcf4f3c5100cd0bf7b5c0bf853e
| Timestamp: 1780392125 | Timestamp [UTC]: 2026-06-02 09:22:05 | Age [y:d:h:m:s]: 00:014:23:53:01 |
| Block: 5218 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3527 | RingCT/type: yes/0 |
| Extra: 018801eb4e862c84641fd7e9b3993f8290b0637bcf4f3c5100cd0bf7b5c0bf853e02090000000126697be300 | ||
1 output(s) for total of 34.836000945263 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8456e8bcae789de53398c1492daf49ad0037ae9740fcdaa2f4126c07f3a1753a | 34.836000945263 | 6603 of 0 | <af> |
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": 5278,
"vin": [ {
"gen": {
"height": 5218
}
}
],
"vout": [ {
"amount": 34836000945263,
"target": {
"tagged_key": {
"key": "8456e8bcae789de53398c1492daf49ad0037ae9740fcdaa2f4126c07f3a1753a",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 136, 1, 235, 78, 134, 44, 132, 100, 31, 215, 233, 179, 153, 63, 130, 144, 176, 99, 123, 207, 79, 60, 81, 0, 205, 11, 247, 181, 192, 191, 133, 62, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}