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: 199e3f8bf24b784761a3f3c721b1feba107930bc923a53d30c658473ab1dd902
Tx prefix hash: f08e948abb888a356dd1866d31d6c28cb273d7479309649166ef2cfb31b02ac3
Tx public key: 1e89cc42ab0c0488c108aef767f678262df553d15da29f839fa3bd2279091c35
| Timestamp: 1779947976 | Timestamp [UTC]: 2026-05-28 05:59:36 | Age [y:d:h:m:s]: 00:011:17:19:17 |
| Block: 3583 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4303 | RingCT/type: yes/0 |
| Extra: 011e89cc42ab0c0488c108aef767f678262df553d15da29f839fa3bd2279091c3502090000000326697be300 | ||
1 output(s) for total of 34.944807209832 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9de43632a31d3e25f8ee6b7f8e83f9ce91900216b2cb9038cb6b6dd34928d03 | 34.944807209832 | 4326 of 0 | <6f> |
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": 3643,
"vin": [ {
"gen": {
"height": 3583
}
}
],
"vout": [ {
"amount": 34944807209832,
"target": {
"tagged_key": {
"key": "d9de43632a31d3e25f8ee6b7f8e83f9ce91900216b2cb9038cb6b6dd34928d03",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 30, 137, 204, 66, 171, 12, 4, 136, 193, 8, 174, 247, 103, 246, 120, 38, 45, 245, 83, 209, 93, 162, 159, 131, 159, 163, 189, 34, 121, 9, 28, 53, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}