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: 98fdc97ec583f71e388da47fc56ee93cda9f6b81291eb8ac8c6a5b9f510f7d75
Tx prefix hash: 0b5109c76985f9eb35a16eb3dfaa2ecf8288a86456c5c8e950c8f61d67ac3209
Tx public key: f6e6a43c7649b7325f1d4c4b33e780ae30b33541b07c77249a97ea0e61ce4c1c
| Timestamp: 1779861858 | Timestamp [UTC]: 2026-05-27 06:04:18 | Age [y:d:h:m:s]: 00:012:19:31:39 |
| Block: 2693 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5193 | RingCT/type: yes/0 |
| Extra: 01f6e6a43c7649b7325f1d4c4b33e780ae30b33541b07c77249a97ea0e61ce4c1c02090000000126697be300 | ||
1 output(s) for total of 35.004177862159 HMNY
| stealth address | amount | amount idx | tag |
| 00: db1a312481d0d14fabf823cb746d5db973aaf4b04089a866fd164481dcb9e414 | 35.004177862159 | 3177 of 0 | <d3> |
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": 2753,
"vin": [ {
"gen": {
"height": 2693
}
}
],
"vout": [ {
"amount": 35004177862159,
"target": {
"tagged_key": {
"key": "db1a312481d0d14fabf823cb746d5db973aaf4b04089a866fd164481dcb9e414",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 246, 230, 164, 60, 118, 73, 183, 50, 95, 29, 76, 75, 51, 231, 128, 174, 48, 179, 53, 65, 176, 124, 119, 36, 154, 151, 234, 14, 97, 206, 76, 28, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}