The Data Availability (DA) Visualizer is a built-in monitoring tool in Evolve that provides real-time insights into blob submissions to the DA layer. It offers a web-based interface for tracking submission statistics, monitoring DA layer health, and analyzing blob details.
Note: Only aggregator nodes submit data to the DA layer. Non-aggregator nodes will not display submission data.
The DA Visualizer provides:
- Real-time monitoring of blob submissions (last 100 submissions)
- Success/failure statistics and trends
- Gas price tracking and cost analysis
- DA layer health monitoring
- Detailed blob inspection capabilities
- Recent submission history
The DA Visualizer is disabled by default. To enable it, use the following configuration:
testapp start --rollkit.rpc.enable_da_visualizationAdd the following to your evnode.yml configuration file:
rpc:
enable_da_visualization: trueOnce enabled, the DA Visualizer is accessible through your node's RPC server. By default, this is:
http://localhost:7331/da
The visualizer provides several API endpoints and a web interface:
Navigate to http://localhost:7331/da in your web browser to access the interactive dashboard.
The following REST API endpoints are available for programmatic access:
GET /da/submissionsReturns the most recent blob submissions (up to 100 kept in memory).
GET /da/blob?id={blob_id}Returns detailed information about a specific blob submission.
GET /da/statsReturns aggregated statistics including:
- Total submissions count
- Success/failure rates
- Average gas price
- Total gas spent
- Average blob size
- Submission trends
GET /da/healthReturns the current health status of the DA layer including:
- Connection status
- Recent error rates
- Performance metrics
- Last successful submission timestamp
The dashboard automatically updates every 30 seconds, displaying:
- Recent submission feed with status indicators (last 100 submissions)
- Success rate percentage
- Current gas price trends
- Submission history
Each submission entry shows:
- Timestamp
- Blob ID with link to detailed view
- Number of blobs in the batch
- Submission status (success/failure)
- Gas price used
- Error messages (if any)
The statistics section provides:
- Performance Metrics: Success rate, average submission time
- Cost Analysis: Total gas spent, average gas price over time
- Volume Metrics: Total blobs submitted, average blob size
- Trend Analysis: Hourly and daily submission patterns
The health status indicator shows:
- 🟢 Healthy: DA layer responding normally
- 🟡 Warning: Some failures but overall functional
- 🔴 Critical: High failure rate or connection issues
- Monitor the reliability of DA submissions
- Track gas costs and optimize gas price settings
- Identify patterns in submission failures
- Ensure DA layer connectivity
- Debug DA submission issues
- Analyze blob data structure
- Monitor application-specific submission patterns
- Test DA layer integration
- Track overall network DA usage
- Identify congestion periods
- Monitor gas price fluctuations
- Analyze submission patterns across the network
When enabling the DA Visualizer, you may want to adjust related RPC settings:
rpc:
address: "0.0.0.0:7331" # Bind to all interfaces for remote access
enable_da_visualization: trueSecurity Note: If binding to all interfaces (0.0.0.0), ensure proper firewall rules are in place to restrict access to trusted sources only.
-
Verify the DA Visualizer is enabled:
- Check your configuration file or ensure the flag is set
- Look for log entries confirming "DA visualization endpoints registered"
-
Check the RPC server is running:
- Verify the RPC address in logs
- Ensure no port conflicts
-
For remote access:
- Ensure the RPC server is bound to an accessible interface
- Check firewall settings
- Verify your node is in aggregator mode (only aggregators submit to DA)
- Check DA layer connectivity in the node logs
- Ensure transactions are being processed
- Note that the visualizer only keeps the last 100 submissions in memory
- 404 Not Found: DA Visualizer not enabled
- 500 Internal Server Error: Check node logs for DA connection issues
- Empty responses: No submissions have been made yet
# Get recent submissions (returns up to 100)
curl http://localhost:7331/da/submissions
# Get specific blob details
curl http://localhost:7331/da/blob?id=abc123...
# Get statistics
curl http://localhost:7331/da/stats
# Check DA health
curl http://localhost:7331/da/health#!/bin/bash
# Simple monitoring script
while true; do
health=$(curl -s http://localhost:7331/da/health | jq -r '.status')
if [ "$health" != "healthy" ]; then
echo "DA layer issue detected: $health"
# Send alert...
fi
sleep 30
doneFor complete DA layer configuration options, see the Config Reference.
For metrics and monitoring setup, see the Metrics Guide.