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: 736869fa33334a41ff7667922d111f127d1acddfb551f18563485d1bfd1c5241
Tx prefix hash: e14d212f6ad17ec2747aafb636ac6fb82fcc3b40400d0432ef46992a1a0864ae
Tx public key: f7063024d180a1dfc7b0d37f390c495d5a99afbdf2f4e27c5254d909f44f70f4
| Timestamp: 1779980272 | Timestamp [UTC]: 2026-05-28 14:57:52 | Age [y:d:h:m:s]: 00:011:11:51:56 |
| Block: 3914 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3986 | RingCT/type: yes/0 |
| Extra: 01f7063024d180a1dfc7b0d37f390c495d5a99afbdf2f4e27c5254d909f44f70f402090000000226697be300 | ||
1 output(s) for total of 34.922752362586 HMNY
| stealth address | amount | amount idx | tag |
| 00: a9baddb9368ea5acc295213119fecb662456e04f4011b4840e63af7c9e10d42d | 34.922752362586 | 4804 of 0 | <3f> |
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": 3974,
"vin": [ {
"gen": {
"height": 3914
}
}
],
"vout": [ {
"amount": 34922752362586,
"target": {
"tagged_key": {
"key": "a9baddb9368ea5acc295213119fecb662456e04f4011b4840e63af7c9e10d42d",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 247, 6, 48, 36, 209, 128, 161, 223, 199, 176, 211, 127, 57, 12, 73, 93, 90, 153, 175, 189, 242, 244, 226, 124, 82, 84, 217, 9, 244, 79, 112, 244, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}