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: ddf3cb25f1ed2f4daaba866de38f422af5d4a18f52275198eb046c7cbe790a78
Tx prefix hash: 84f8d0dbd8740e96705a6d0c8c0b6bec80fe69d69af08ff1bebb1f21d228ca86
Tx public key: 241b317f785e12ad95beb33aab591e425deb0ea4ec73cb9383f3439ff83aaa8f
| Timestamp: 1779461311 | Timestamp [UTC]: 2026-05-22 14:48:31 | Age [y:d:h:m:s]: 00:021:20:13:45 |
| Block: 443 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8302 | RingCT/type: yes/0 |
| Extra: 01241b317f785e12ad95beb33aab591e425deb0ea4ec73cb9383f3439ff83aaa8f02090000000493369e7d00 | ||
1 output(s) for total of 35.154722442576 HMNY
| stealth address | amount | amount idx | tag |
| 00: b4f94dd437b23613056eb4d30f4430562e9560fa5759c97f420cea3b6ec31999 | 35.154722442576 | 447 of 0 | <e2> |
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": 503,
"vin": [ {
"gen": {
"height": 443
}
}
],
"vout": [ {
"amount": 35154722442576,
"target": {
"tagged_key": {
"key": "b4f94dd437b23613056eb4d30f4430562e9560fa5759c97f420cea3b6ec31999",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 36, 27, 49, 127, 120, 94, 18, 173, 149, 190, 179, 58, 171, 89, 30, 66, 93, 235, 14, 164, 236, 115, 203, 147, 131, 243, 67, 159, 248, 58, 170, 143, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}