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: 2908bef57253cded68b6f38b92611269d81eb2b94152c452ad53e7fb32bc9c6a
Tx prefix hash: b74f70796262b7e5e680728af321898134f4e05ffa75c5eb2e8d3524892593eb
Tx public key: 4b83edfa72d7879247eaa1c4093b1dc174213ad1d57059300e692a96a3f46e4b
| Timestamp: 1779955192 | Timestamp [UTC]: 2026-05-28 07:59:52 | Age [y:d:h:m:s]: 00:011:19:38:58 |
| Block: 3680 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4267 | RingCT/type: yes/0 |
| Extra: 014b83edfa72d7879247eaa1c4093b1dc174213ad1d57059300e692a96a3f46e4b02090000000226697be300 | ||
1 output(s) for total of 34.938342564471 HMNY
| stealth address | amount | amount idx | tag |
| 00: 12688a200a57931937a07f9acde48d5359ac75089773296feb0bd09e2e8b6855 | 34.938342564471 | 4450 of 0 | <4a> |
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": 3740,
"vin": [ {
"gen": {
"height": 3680
}
}
],
"vout": [ {
"amount": 34938342564471,
"target": {
"tagged_key": {
"key": "12688a200a57931937a07f9acde48d5359ac75089773296feb0bd09e2e8b6855",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 75, 131, 237, 250, 114, 215, 135, 146, 71, 234, 161, 196, 9, 59, 29, 193, 116, 33, 58, 209, 213, 112, 89, 48, 14, 105, 42, 150, 163, 244, 110, 75, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}