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: c812d57bae9737c7b49194aee10f7457fbb6040eb2aa6a2f161d5fbefcd72f15
Tx prefix hash: 24d12c346efb6afda92d3848f6414ec18d7ed460d5fe839210ae26029125fdb5
Tx public key: 1995a9d6d82ef93ad0b29e3d7a3ca7031674faf87f1be08a3e27d3cb328a3abb
| Timestamp: 1779643892 | Timestamp [UTC]: 2026-05-24 17:31:32 | Age [y:d:h:m:s]: 00:019:17:30:44 |
| Block: 1422 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7323 | RingCT/type: yes/0 |
| Extra: 011995a9d6d82ef93ad0b29e3d7a3ca7031674faf87f1be08a3e27d3cb328a3abb020900000001ba6d17be00 | ||
1 output(s) for total of 35.089139417252 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5475445410ca7d393b2ca98be5ad08d9709ef830f6f2e21b1729f05b19fc6195 | 35.089139417252 | 1574 of 0 | <6c> |
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": 1482,
"vin": [ {
"gen": {
"height": 1422
}
}
],
"vout": [ {
"amount": 35089139417252,
"target": {
"tagged_key": {
"key": "5475445410ca7d393b2ca98be5ad08d9709ef830f6f2e21b1729f05b19fc6195",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 25, 149, 169, 214, 216, 46, 249, 58, 208, 178, 158, 61, 122, 60, 167, 3, 22, 116, 250, 248, 127, 27, 224, 138, 62, 39, 211, 203, 50, 138, 58, 187, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}