Problem to solve

On current eden testnet the sequencer sporadically fails to submit blobs to the DA layer and the feedback is a repetitive log line

The log does not contain:

• What is the transaction that is rejected
• What causes the rejection
• The recommended remediation

As a result operators may have a hard time deciding what to do next

Proposed solution or feature

1. Prometheus metrics (all under da_submitter_*)

   • da_submitter_failures_total{reason="already_rejected|insufficient_fee|timeout|...|unknown"}
   • da_submitter_last_failure_timestamp{reason="..."}
   • da_submitter_pending_blobs (gauge)
   • da_submitter_resends_total (counter incremented on every re-broadcast attempt)

2. Structured error details
   Extend the returned error so that the log line contains:

   • What is the transaction that is rejected
   • What is the probable cause for the rejection
   • Suggested action (wait, augment da block time, clear local cache, escalate to celestia-node, escalate to devs)

3. DA endpoint
   Expose every submission attempt and retries with technical details on the da_visualization RCP Endpoint

Alternatives considered

No response

Additional context

No response