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: 8ff2b65847bebaa7995fcff587a9b33dd4d0549b3c1cf9293f5b3250da2f3a58
Tx prefix hash: e35a9234b203d900b4e89eda74e4fd64017d3e93b2ab66f577e1d485ea60518c
Tx public key: 8e0a3ff490a2eabd801476e581d00db344e4a798cf77448978f7467b470ea4a4
| Timestamp: 1780810179 | Timestamp [UTC]: 2026-06-07 05:29:39 | Age [y:d:h:m:s]: 00:001:20:06:18 |
| Block: 7009 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 877 | RingCT/type: yes/0 |
| Extra: 018e0a3ff490a2eabd801476e581d00db344e4a798cf77448978f7467b470ea4a4020900000002e49593ff00 | ||
1 output(s) for total of 34.726224741632 HMNY
| stealth address | amount | amount idx | tag |
| 00: 98fd25d51d04518b9f58b56d38fc38132dc725127bd5d0ff9afa6105e4587fe4 | 34.726224741632 | 8643 of 0 | <05> |
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": 7069,
"vin": [ {
"gen": {
"height": 7009
}
}
],
"vout": [ {
"amount": 34726224741632,
"target": {
"tagged_key": {
"key": "98fd25d51d04518b9f58b56d38fc38132dc725127bd5d0ff9afa6105e4587fe4",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 142, 10, 63, 244, 144, 162, 234, 189, 128, 20, 118, 229, 129, 208, 13, 179, 68, 228, 167, 152, 207, 119, 68, 137, 120, 247, 70, 123, 71, 14, 164, 164, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}