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: a4dbec23fe420d85b5d245d39b72295d06d8ad31057e0aecbc738aad1b76e178
Tx prefix hash: 590f9d8bbf37fd6d2a2b09ef4eb2e4e33ed79181a984b0c359998b0a8df8e737
Tx public key: fcf8a95df38cdd45aa7718fd9999f47b5a43c8d13f7df4224bb6e3a74aa9bc6b
| Timestamp: 1780688202 | Timestamp [UTC]: 2026-06-05 19:36:42 | Age [y:d:h:m:s]: 00:003:08:02:08 |
| Block: 5515 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2432 | RingCT/type: yes/0 |
| Extra: 01fcf8a95df38cdd45aa7718fd9999f47b5a43c8d13f7df4224bb6e3a74aa9bc6b020900000001e49593ff00 | ||
1 output(s) for total of 34.816272528441 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30bcfb1bec8bcd675298e22806bcbdb37ad5384c55f48b0705b2765957906909 | 34.816272528441 | 6956 of 0 | <59> |
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": 5575,
"vin": [ {
"gen": {
"height": 5515
}
}
],
"vout": [ {
"amount": 34816272528441,
"target": {
"tagged_key": {
"key": "30bcfb1bec8bcd675298e22806bcbdb37ad5384c55f48b0705b2765957906909",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 252, 248, 169, 93, 243, 140, 221, 69, 170, 119, 24, 253, 153, 153, 244, 123, 90, 67, 200, 209, 63, 125, 244, 34, 75, 182, 227, 167, 74, 169, 188, 107, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}