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: baa4296d79059e5ad3ea38e1385341c997192bd51268b9063366ccef9306e426
Tx prefix hash: 272ccfab01b51673235c97bb49bef67f0f0781cb9eefdf4ef715f6e75ceafd85
Tx public key: 574b9abff1077fee2ee9cac4fe96afbf7b49c4e1e7f1e0cd3891dba87d78c321
| Timestamp: 1780907697 | Timestamp [UTC]: 2026-06-08 08:34:57 | Age [y:d:h:m:s]: 00:001:00:40:04 |
| Block: 7886 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 470 | RingCT/type: yes/0 |
| Extra: 01574b9abff1077fee2ee9cac4fe96afbf7b49c4e1e7f1e0cd3891dba87d78c321020900000002e49593ff00 | ||
1 output(s) for total of 34.659177412622 HMNY
| stealth address | amount | amount idx | tag |
| 00: c075cf46ce3fac3ea2d8a38a2a1cd70befebdf5d1d3f3839428471e82d3b2517 | 34.659177412622 | 9778 of 0 | <06> |
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": 7946,
"vin": [ {
"gen": {
"height": 7886
}
}
],
"vout": [ {
"amount": 34659177412622,
"target": {
"tagged_key": {
"key": "c075cf46ce3fac3ea2d8a38a2a1cd70befebdf5d1d3f3839428471e82d3b2517",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 87, 75, 154, 191, 241, 7, 127, 238, 46, 233, 202, 196, 254, 150, 175, 191, 123, 73, 196, 225, 231, 241, 224, 205, 56, 145, 219, 168, 125, 120, 195, 33, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}