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: 484fa9183a866de98d3a173ddb6831fa712685252e82f5bc338b75dde41594a0
Tx prefix hash: 7ea582c7ba694280e1a71b563e92a56d8ae875fbf60b1195fa1cd623d748d0cb
Tx public key: 8fff345fc63035338ebeb4e50a720beba23098ef913e3653e73edcd4aa6e4b51
| Timestamp: 1780814075 | Timestamp [UTC]: 2026-06-07 06:34:35 | Age [y:d:h:m:s]: 00:010:01:30:46 |
| Block: 7023 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1722 | RingCT/type: yes/0 |
| Extra: 018fff345fc63035338ebeb4e50a720beba23098ef913e3653e73edcd4aa6e4b51020900000001e49593ff00 | ||
1 output(s) for total of 34.718895703818 HMNY
| stealth address | amount | amount idx | tag |
| 00: c6edd0b99377f90944d17ccd550eff220287fb60e85d899aa3fb623d3c29a2e1 | 34.718895703818 | 8661 of 0 | <86> |
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": 7083,
"vin": [ {
"gen": {
"height": 7023
}
}
],
"vout": [ {
"amount": 34718895703818,
"target": {
"tagged_key": {
"key": "c6edd0b99377f90944d17ccd550eff220287fb60e85d899aa3fb623d3c29a2e1",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 143, 255, 52, 95, 198, 48, 53, 51, 142, 190, 180, 229, 10, 114, 11, 235, 162, 48, 152, 239, 145, 62, 54, 83, 231, 62, 220, 212, 170, 110, 75, 81, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}