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: e104fc3406fd164b632b793f3d07288605bbde957fd035ac972cbd190ee71bae
Tx prefix hash: 98318a2f0bf4b5dc4b714c7cf09c5758eddf4bf0b2a734e190947f45b6bad8b6
Tx public key: 4dc8ebffe795514a5b2051fdf8912c6c1e3e0f56d1a26d9f7f4f00c11cd67667
| Timestamp: 1779795228 | Timestamp [UTC]: 2026-05-26 11:33:48 | Age [y:d:h:m:s]: 00:013:16:17:10 |
| Block: 2262 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5729 | RingCT/type: yes/0 |
| Extra: 014dc8ebffe795514a5b2051fdf8912c6c1e3e0f56d1a26d9f7f4f00c11cd6766702090000000326697be300 | ||
1 output(s) for total of 35.032965509293 HMNY
| stealth address | amount | amount idx | tag |
| 00: f32bd8e42b442c004cfda6f365ceab824b9e306bfd8ffa40ebba0955fde59822 | 35.032965509293 | 2628 of 0 | <3b> |
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": 2322,
"vin": [ {
"gen": {
"height": 2262
}
}
],
"vout": [ {
"amount": 35032965509293,
"target": {
"tagged_key": {
"key": "f32bd8e42b442c004cfda6f365ceab824b9e306bfd8ffa40ebba0955fde59822",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 77, 200, 235, 255, 231, 149, 81, 74, 91, 32, 81, 253, 248, 145, 44, 108, 30, 62, 15, 86, 209, 162, 109, 159, 127, 79, 0, 193, 28, 214, 118, 103, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}