📡
beaconcha.in Knowledge Base
  • 👋Welcome
  • 🖥️v2 beaconcha.in explorer [BETA]
    • 🎉Introducing v2-beta
    • 🦸Summary view
    • 🟩Slot visualization
    • 🫂Validator groups
    • ⚒️Manage Validators
    • ⚒️Manage Validators [API]
    • 🤝Share your custom dashboard
    • 📈Metric: Validator Efficiency
    • ⏰Notifications v2
  • v1 beaconcha.in Explorer
    • Notifications
      • Understanding notifications
      • Notification configuration
    • Mobile App <> Node Monitoring
    • Optimal Inclusion Distance
  • Ethereum Staking
    • Glossary
    • The Genesis Event
    • Ethereum Validator Keys
    • Deposit Process
    • Rewards and Penalties
    • Attestation
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. v1 beaconcha.in Explorer

Optimal Inclusion Distance

Last updated 1 year ago

Was this helpful?

The attestation for slot 156508 was included in slot 156510 but why is the inclusion distance 0? If were to use the formula from above and set the inclusion delay to 0, the rewards would be 0 for a proposed attestation

Missed blocks are not added to the inclusion distance, but since the attestant is not responsible for the block proposal, and to only warn the user about its faults (e.g. slow internet connection, power failure etc.), the displays the distance as 0

beaconcha.in explorer