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: 7a355e06e99ae7c5c26f93734d72062f4adcea5a737bd1e7ca8f43538c336606
Tx prefix hash: 1e1fdadab73f3e92d1e2c36bca1addb457dfe0ef21d49c193947f1a1ad548073
Tx public key: fc52f34b1c4ed1c369c5b62a57c55ef5c7ff969e83da2696b6c7da5a529e4f77
| Timestamp: 1779441150 | Timestamp [UTC]: 2026-05-22 09:12:30 | Age [y:d:h:m:s]: 00:017:15:34:17 |
| Block: 212 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7674 | RingCT/type: yes/0 |
| Extra: 01fc52f34b1c4ed1c369c5b62a57c55ef5c7ff969e83da2696b6c7da5a529e4f77020900000002c3b6d28a00 | ||
1 output(s) for total of 35.170214954104 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2907ff35aa4eaafe37ef74bd60381bfc073202915809c57839324289c445b854 | 35.170214954104 | 208 of 0 | <2a> |
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": 272,
"vin": [ {
"gen": {
"height": 212
}
}
],
"vout": [ {
"amount": 35170214954104,
"target": {
"tagged_key": {
"key": "2907ff35aa4eaafe37ef74bd60381bfc073202915809c57839324289c445b854",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 252, 82, 243, 75, 28, 78, 209, 195, 105, 197, 182, 42, 87, 197, 94, 245, 199, 255, 150, 158, 131, 218, 38, 150, 182, 199, 218, 90, 82, 158, 79, 119, 2, 9, 0, 0, 0, 2, 195, 182, 210, 138, 0
],
"rct_signatures": {
"type": 0
}
}