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: 62708240f2cf71cd72af186f21e2e32cfae5700f62fe2932793296599a1c928c
Tx prefix hash: 10735ce9964ccd94470f854fb59fdcac60ab1baf45fe84131004e7469f9db2f2
Tx public key: d27b04f61874fb6257cb261ee3603c96dc5ac84e5d46df23012eb39335f627e5
| Timestamp: 1779449630 | Timestamp [UTC]: 2026-05-22 11:33:50 | Age [y:d:h:m:s]: 00:017:14:02:07 |
| Block: 309 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7577 | RingCT/type: yes/0 |
| Extra: 01d27b04f61874fb6257cb261ee3603c96dc5ac84e5d46df23012eb39335f627e50209000000014438f87f00 | ||
1 output(s) for total of 35.163708609240 HMNY
| stealth address | amount | amount idx | tag |
| 00: e8b45984f13b745cae411180da38df59501a9c3c9b88a534a9fca649c9288415 | 35.163708609240 | 305 of 0 | <96> |
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": 369,
"vin": [ {
"gen": {
"height": 309
}
}
],
"vout": [ {
"amount": 35163708609240,
"target": {
"tagged_key": {
"key": "e8b45984f13b745cae411180da38df59501a9c3c9b88a534a9fca649c9288415",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 210, 123, 4, 246, 24, 116, 251, 98, 87, 203, 38, 30, 227, 96, 60, 150, 220, 90, 200, 78, 93, 70, 223, 35, 1, 46, 179, 147, 53, 246, 39, 229, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}