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: f732cadd3a366cb8cf94021fc40b72f94b3a596b5d0557a4c2dc770371f4859b
Tx prefix hash: da5d0c11784e77b4f7084f6254bed506f8ebdcd8bf5e61378925d3dcb24bf667
Tx public key: 315798b1a0e1c4bcb468604709e827f5433dbc795d941b03c631214e8f95ca5b
| Timestamp: 1779724670 | Timestamp [UTC]: 2026-05-25 15:57:50 | Age [y:d:h:m:s]: 00:014:10:42:46 |
| Block: 1830 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6067 | RingCT/type: yes/0 |
| Extra: 01315798b1a0e1c4bcb468604709e827f5433dbc795d941b03c631214e8f95ca5b020900000001ba6d17be00 | ||
1 output(s) for total of 35.061843706721 HMNY
| stealth address | amount | amount idx | tag |
| 00: da0299e432c5b73372096563911a0f3b806620c1f245b0cedbee892a9017a41d | 35.061843706721 | 2024 of 0 | <da> |
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": 1890,
"vin": [ {
"gen": {
"height": 1830
}
}
],
"vout": [ {
"amount": 35061843706721,
"target": {
"tagged_key": {
"key": "da0299e432c5b73372096563911a0f3b806620c1f245b0cedbee892a9017a41d",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 49, 87, 152, 177, 160, 225, 196, 188, 180, 104, 96, 71, 9, 232, 39, 245, 67, 61, 188, 121, 93, 148, 27, 3, 198, 49, 33, 78, 143, 149, 202, 91, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}