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: b0450ed8b5a6c2c89935087968e4fac5e4b18b71d5a27c319a59f4d66f4d1a61
Tx prefix hash: 0c06706f23c7a8069dd0953ddfd682c704463c476a1dbcdd35bf535a95c3be4c
Tx public key: b80663cb73fcd1a9e9ae8ed874079a8cd604ec198e168e9b32eb25df3e74a472
| Timestamp: 1779890961 | Timestamp [UTC]: 2026-05-27 14:09:21 | Age [y:d:h:m:s]: 00:012:12:40:27 |
| Block: 3061 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4859 | RingCT/type: yes/0 |
| Extra: 01b80663cb73fcd1a9e9ae8ed874079a8cd604ec198e168e9b32eb25df3e74a47202090000000326697be300 | ||
1 output(s) for total of 34.979616876625 HMNY
| stealth address | amount | amount idx | tag |
| 00: d577f093785eb8afefa534d3e83b7b208d09f547694aba88f5f70f24c42ec15f | 34.979616876625 | 3643 of 0 | <bc> |
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": 3121,
"vin": [ {
"gen": {
"height": 3061
}
}
],
"vout": [ {
"amount": 34979616876625,
"target": {
"tagged_key": {
"key": "d577f093785eb8afefa534d3e83b7b208d09f547694aba88f5f70f24c42ec15f",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 184, 6, 99, 203, 115, 252, 209, 169, 233, 174, 142, 216, 116, 7, 154, 140, 214, 4, 236, 25, 142, 22, 142, 155, 50, 235, 37, 223, 62, 116, 164, 114, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}