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: 337cf08d18fbfc6b61ecc6d97945ddea7936fad75b1f9b976bb539fc935dc5eb
Tx prefix hash: db16c64bcd2f84350776552dec3b4e6cbe96b64822d7554714cff3dd76d0d6ba
Tx public key: 2e42331a56f9d0facfe0e6da2ab5df6d061ee982db673019f73c5fb60ba60293
| Timestamp: 1780007491 | Timestamp [UTC]: 2026-05-28 22:31:31 | Age [y:d:h:m:s]: 00:011:03:04:26 |
| Block: 4084 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3802 | RingCT/type: yes/0 |
| Extra: 012e42331a56f9d0facfe0e6da2ab5df6d061ee982db673019f73c5fb60ba6029302090000000426697be300 | ||
1 output(s) for total of 34.914046510564 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8256696b2e01b12f67a40ed8b1283655ec225082143ca6714e50083ec12a5273 | 34.914046510564 | 5072 of 0 | <33> |
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": 4144,
"vin": [ {
"gen": {
"height": 4084
}
}
],
"vout": [ {
"amount": 34914046510564,
"target": {
"tagged_key": {
"key": "8256696b2e01b12f67a40ed8b1283655ec225082143ca6714e50083ec12a5273",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 46, 66, 51, 26, 86, 249, 208, 250, 207, 224, 230, 218, 42, 181, 223, 109, 6, 30, 233, 130, 219, 103, 48, 25, 247, 60, 95, 182, 11, 166, 2, 147, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}