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: 8cb8ea90df6f9ea07ec3363c478082c5c3689a3f1a3daa67691b4a1533446c7c
Tx prefix hash: 80c658a4b9a3260339ba613f5be6937af16abf7f862b06ca8ba33d16b952ce85
Tx public key: f92a3b0b2171cb65c45e904ec9402df4a63dae61eecb1decc2ee768716de1b30
| Timestamp: 1780027830 | Timestamp [UTC]: 2026-05-29 04:10:30 | Age [y:d:h:m:s]: 00:010:20:36:17 |
| Block: 4180 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3706 | RingCT/type: yes/0 |
| Extra: 01f92a3b0b2171cb65c45e904ec9402df4a63dae61eecb1decc2ee768716de1b3002090000000626697be300 | ||
1 output(s) for total of 34.905038615833 HMNY
| stealth address | amount | amount idx | tag |
| 00: be38d3a87892f43a93222d5e8504daeb35387122871dafa8b4d2f2fe2905dd32 | 34.905038615833 | 5213 of 0 | <7b> |
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": 4240,
"vin": [ {
"gen": {
"height": 4180
}
}
],
"vout": [ {
"amount": 34905038615833,
"target": {
"tagged_key": {
"key": "be38d3a87892f43a93222d5e8504daeb35387122871dafa8b4d2f2fe2905dd32",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 249, 42, 59, 11, 33, 113, 203, 101, 196, 94, 144, 78, 201, 64, 45, 244, 166, 61, 174, 97, 238, 203, 29, 236, 194, 238, 118, 135, 22, 222, 27, 48, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}