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: 4f2e12dc0475c47bb9e4e6037a47ce2aac4733ae81c940fd2cf8b7360198ff22
Tx prefix hash: 83bc8f6a6c9f97763948b5e828db5224944d6b570800053dce2efeb68f3f044a
Tx public key: 733ab7fa6f2d80ff311f9068338abded81b1ff42f2b57948bd26b06fa013d239
| Timestamp: 1779432049 | Timestamp [UTC]: 2026-05-22 06:40:49 | Age [y:d:h:m:s]: 00:018:10:28:14 |
| Block: 34 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 8700 | RingCT/type: yes/0 |
| Extra: 01733ab7fa6f2d80ff311f9068338abded81b1ff42f2b57948bd26b06fa013d239 | ||
1 output(s) for total of 35.182157564016 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6841c5fd926cf3bb72d12018d5c1e1e15742655aaa210c4efc84408ff1d16e37 | 35.182157564016 | 30 of 0 | <89> |
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": 94,
"vin": [ {
"gen": {
"height": 34
}
}
],
"vout": [ {
"amount": 35182157564016,
"target": {
"tagged_key": {
"key": "6841c5fd926cf3bb72d12018d5c1e1e15742655aaa210c4efc84408ff1d16e37",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 115, 58, 183, 250, 111, 45, 128, 255, 49, 31, 144, 104, 51, 138, 189, 237, 129, 177, 255, 66, 242, 181, 121, 72, 189, 38, 176, 111, 160, 19, 210, 57
],
"rct_signatures": {
"type": 0
}
}