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: 2c59bcfc0a475e888445f537a18127c47395586eef855e7e46e91e5601fd92d5
Tx prefix hash: da81bca82c2f87be8d29d2f86019bf29ea860311d02bdabdbe0cba0b236bbde2
Tx public key: ab751bf51a76b969d598d5650fcdefaab0141f15a5237c35297b9a75f44f13d6
| Timestamp: 1779806375 | Timestamp [UTC]: 2026-05-26 14:39:35 | Age [y:d:h:m:s]: 00:013:12:01:01 |
| Block: 2352 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5545 | RingCT/type: yes/0 |
| Extra: 01ab751bf51a76b969d598d5650fcdefaab0141f15a5237c35297b9a75f44f13d602090000000226697be300 | ||
1 output(s) for total of 35.026952212600 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5ec24b99530d9df19caf6045a2b629f062b8202850aba0783ba88f297c6aef6 | 35.026952212600 | 2756 of 0 | <b6> |
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": 2412,
"vin": [ {
"gen": {
"height": 2352
}
}
],
"vout": [ {
"amount": 35026952212600,
"target": {
"tagged_key": {
"key": "c5ec24b99530d9df19caf6045a2b629f062b8202850aba0783ba88f297c6aef6",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 171, 117, 27, 245, 26, 118, 185, 105, 213, 152, 213, 101, 15, 205, 239, 170, 176, 20, 31, 21, 165, 35, 124, 53, 41, 123, 154, 117, 244, 79, 19, 214, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}