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: f210e9091005509c9fd1dc11fcfe9ba1cb784dcf541ac1e095e3fdc66cf2f128
Tx prefix hash: 2d6cad9f822b8b49404b0765674b113e771b31f895a62bd8ca30bbf490ac9b85
Tx public key: 03a29135e278f7ecdcbf258f550fa50a8f7f01423ad9e48ef2e81d3ad3f10362
| Timestamp: 1779966512 | Timestamp [UTC]: 2026-05-28 11:08:32 | Age [y:d:h:m:s]: 00:011:14:27:25 |
| Block: 3809 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4077 | RingCT/type: yes/0 |
| Extra: 0103a29135e278f7ecdcbf258f550fa50a8f7f01423ad9e48ef2e81d3ad3f1036202090000000226697be300 | ||
1 output(s) for total of 34.933072305375 HMNY
| stealth address | amount | amount idx | tag |
| 00: 96b2b9315ff32b3ebc17f08d54705985e6210c2d537f522358808206a17bf834 | 34.933072305375 | 4635 of 0 | <c5> |
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": 3869,
"vin": [ {
"gen": {
"height": 3809
}
}
],
"vout": [ {
"amount": 34933072305375,
"target": {
"tagged_key": {
"key": "96b2b9315ff32b3ebc17f08d54705985e6210c2d537f522358808206a17bf834",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 3, 162, 145, 53, 226, 120, 247, 236, 220, 191, 37, 143, 85, 15, 165, 10, 143, 127, 1, 66, 58, 217, 228, 142, 242, 232, 29, 58, 211, 241, 3, 98, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}