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: 24e5ff687f64d55bb50573b25864a55ecaddf31be2301b3d42e3d1513368f71a
Tx prefix hash: 6df7ce5c27a027a83a11187d0edeb1649b6990bce5772b3ac818d000abb7f094
Tx public key: aa829ddc4cc59e2ece01f9e4741823f72474f5006be73381209dd5f3559a3dc4
| Timestamp: 1779641724 | Timestamp [UTC]: 2026-05-24 16:55:24 | Age [y:d:h:m:s]: 00:015:09:54:24 |
| Block: 1357 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6563 | RingCT/type: yes/0 |
| Extra: 01aa829ddc4cc59e2ece01f9e4741823f72474f5006be73381209dd5f3559a3dc4020900000001ba6d17be00 | ||
1 output(s) for total of 35.093489960517 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8372c6f5176ef149d6a6a7225fb537cf8bc79919594df9186930731345b51a0f | 35.093489960517 | 1507 of 0 | <b6> |
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": 1417,
"vin": [ {
"gen": {
"height": 1357
}
}
],
"vout": [ {
"amount": 35093489960517,
"target": {
"tagged_key": {
"key": "8372c6f5176ef149d6a6a7225fb537cf8bc79919594df9186930731345b51a0f",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 170, 130, 157, 220, 76, 197, 158, 46, 206, 1, 249, 228, 116, 24, 35, 247, 36, 116, 245, 0, 107, 231, 51, 129, 32, 157, 213, 243, 85, 154, 61, 196, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}