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: 4062428ffdbce338267a88a700a5adbef3781d3399d21c691c68eb9229c5d74c
Tx prefix hash: de5280949ca265597898b82dc897604d4ac6b3f016ff5be290695474cd71df66
Tx public key: f43666acf041c7f4ccfff003061385fa06825753e2e9f9c6c3c1d2470be3816e
| Timestamp: 1780685653 | Timestamp [UTC]: 2026-06-05 18:54:13 | Age [y:d:h:m:s]: 00:003:07:55:35 |
| Block: 5393 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2527 | RingCT/type: yes/0 |
| Extra: 01f43666acf041c7f4ccfff003061385fa06825753e2e9f9c6c3c1d2470be3816e020900000002e49593ff00 | ||
1 output(s) for total of 34.824375104769 HMNY
| stealth address | amount | amount idx | tag |
| 00: fd5728d9d90dee387c06c7e27ca39cf73bc388fc6f182b0ebca2dc4659a8bf88 | 34.824375104769 | 6830 of 0 | <b5> |
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": 5453,
"vin": [ {
"gen": {
"height": 5393
}
}
],
"vout": [ {
"amount": 34824375104769,
"target": {
"tagged_key": {
"key": "fd5728d9d90dee387c06c7e27ca39cf73bc388fc6f182b0ebca2dc4659a8bf88",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 244, 54, 102, 172, 240, 65, 199, 244, 204, 255, 240, 3, 6, 19, 133, 250, 6, 130, 87, 83, 226, 233, 249, 198, 195, 193, 210, 71, 11, 227, 129, 110, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}