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: 818537a7ff0708e505c87f49e3830b85388dd8215fe2e01b8b84f9b1d1da624d
Tx prefix hash: 3afb574eafeac804f001b1005663e6db0be6ee20690e0889a6411c40b23a6f5f
Tx public key: 8df3dca638a939ad0cc3d21c81a8be51c904bee9bdaba1dd1fbefe1f6a675748
| Timestamp: 1779532540 | Timestamp [UTC]: 2026-05-23 10:35:40 | Age [y:d:h:m:s]: 00:016:16:14:08 |
| Block: 683 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7237 | RingCT/type: yes/0 |
| Extra: 018df3dca638a939ad0cc3d21c81a8be51c904bee9bdaba1dd1fbefe1f6a675748020900000035ba6d17be00 | ||
1 output(s) for total of 35.141236355138 HMNY
| stealth address | amount | amount idx | tag |
| 00: fcc5390db8a03a9578c391c232fa1793a4cfba37ef6c9566b19bf179030444bd | 35.141236355138 | 762 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": 743,
"vin": [ {
"gen": {
"height": 683
}
}
],
"vout": [ {
"amount": 35141236355138,
"target": {
"tagged_key": {
"key": "fcc5390db8a03a9578c391c232fa1793a4cfba37ef6c9566b19bf179030444bd",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 141, 243, 220, 166, 56, 169, 57, 173, 12, 195, 210, 28, 129, 168, 190, 81, 201, 4, 190, 233, 189, 171, 161, 221, 31, 190, 254, 31, 106, 103, 87, 72, 2, 9, 0, 0, 0, 53, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}