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: 2c90f24db2981183574707635d29e26363ea1bea60993e07dc114be3039aea99
Tx prefix hash: 15fca65d92a9fa06dfff1698e9a2393c2649e8052a1710684bd4de41727f6538
Tx public key: db83324a1872327fa9f981b80e3977e8d053f1c8080e3e8c82f71ddb194f139c
| Timestamp: 1780057858 | Timestamp [UTC]: 2026-05-29 12:30:58 | Age [y:d:h:m:s]: 00:010:13:04:59 |
| Block: 4478 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3408 | RingCT/type: yes/0 |
| Extra: 01db83324a1872327fa9f981b80e3977e8d053f1c8080e3e8c82f71ddb194f139c02090000000226697be300 | ||
1 output(s) for total of 34.885204563040 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e967dff8d172c33277b7cae882f90dd1ac9b57af48b4193c6d3fc264c3e67d0 | 34.885204563040 | 5611 of 0 | <e8> |
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": 4538,
"vin": [ {
"gen": {
"height": 4478
}
}
],
"vout": [ {
"amount": 34885204563040,
"target": {
"tagged_key": {
"key": "5e967dff8d172c33277b7cae882f90dd1ac9b57af48b4193c6d3fc264c3e67d0",
"view_tag": "e8"
}
}
}
],
"extra": [ 1, 219, 131, 50, 74, 24, 114, 50, 127, 169, 249, 129, 184, 14, 57, 119, 232, 208, 83, 241, 200, 8, 14, 62, 140, 130, 247, 29, 219, 25, 79, 19, 156, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}