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: a84d1f879a7006d15f67eb967c7e5c963db16d74c8667d357b535bada5e6e985
Tx prefix hash: 337eb91a095ea8b65f3718997ef299f11f65451ca21bd06b9f12aec1434320c8
Tx public key: 89b565c3ca972c10acd238991dd3aecbdfe5347d373d566ba7f0e2968687d4e3
| Timestamp: 1780323361 | Timestamp [UTC]: 2026-06-01 14:16:01 | Age [y:d:h:m:s]: 00:007:10:30:46 |
| Block: 5119 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2767 | RingCT/type: yes/0 |
| Extra: 0189b565c3ca972c10acd238991dd3aecbdfe5347d373d566ba7f0e2968687d4e302090000002526697be300 | ||
1 output(s) for total of 34.842579568108 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6f18d831b9daaa6f59e2f3a56f611295b995ca5a774650002ba475e6da6d3d44 | 34.842579568108 | 6494 of 0 | <bb> |
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": 5179,
"vin": [ {
"gen": {
"height": 5119
}
}
],
"vout": [ {
"amount": 34842579568108,
"target": {
"tagged_key": {
"key": "6f18d831b9daaa6f59e2f3a56f611295b995ca5a774650002ba475e6da6d3d44",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 137, 181, 101, 195, 202, 151, 44, 16, 172, 210, 56, 153, 29, 211, 174, 203, 223, 229, 52, 125, 55, 61, 86, 107, 167, 240, 226, 150, 134, 135, 212, 227, 2, 9, 0, 0, 0, 37, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}