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: 7f2408f2bc3289264f7500950c968ba936fa00ba9eed353fd06b4c0bb6534575
Tx prefix hash: 0e606d9029cdbd8460ee1f93e8ad0c30f1dc57f744027b6228c88b164938063f
Tx public key: 91ca14e8ff3ad2908dee1b1450f1b98b2a65a79154b9a614c384ea7aa56737b3
| Timestamp: 1780393748 | Timestamp [UTC]: 2026-06-02 09:49:08 | Age [y:d:h:m:s]: 00:006:15:46:49 |
| Block: 5230 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2656 | RingCT/type: yes/0 |
| Extra: 0191ca14e8ff3ad2908dee1b1450f1b98b2a65a79154b9a614c384ea7aa56737b302090000000126697be300 | ||
1 output(s) for total of 34.835203620842 HMNY
| stealth address | amount | amount idx | tag |
| 00: cc51f67064b85ad3a112eb4791ab5d29bf37ed1d896f5f861016b94001660b56 | 34.835203620842 | 6621 of 0 | <3d> |
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": 5290,
"vin": [ {
"gen": {
"height": 5230
}
}
],
"vout": [ {
"amount": 34835203620842,
"target": {
"tagged_key": {
"key": "cc51f67064b85ad3a112eb4791ab5d29bf37ed1d896f5f861016b94001660b56",
"view_tag": "3d"
}
}
}
],
"extra": [ 1, 145, 202, 20, 232, 255, 58, 210, 144, 141, 238, 27, 20, 80, 241, 185, 139, 42, 101, 167, 145, 84, 185, 166, 20, 195, 132, 234, 122, 165, 103, 55, 179, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}