proxmox/docs/04-configuration/SOLACESCANSCOUT_REVIEW.md

SolaceScanScout Navigation & Sync Status Review

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

---

Date: 2026-01-30
Explorer URL: https://explorer.d-bis.org
Status: ✅ FIXED: Explorer now syncing in real-time

---

Navigation Bar Review

Current Navigation Structure

Live Explorer (HTML/JS version):

SolaceScanScout
The Defi Oracle Meta Explorer

Navigation Links:
├── 🏠 Home
├── 🧱 Blocks
├── 🔄 Transactions
├── 🌉 Bridge (Bridge Monitoring)
└── 🪙 WETH (WETH Utilities)

Search Box: Center (address/tx hash/block number)

Next.js Frontend (layout.tsx - not deployed):

SolaceScanScout
The Defi Oracle Meta Explorer

Navigation Links:
├── Blocks
├── Transactions
├── Search
└── Wallet (NEW - MetaMask integration)

Navigation Features

Feature	Status	Notes
Logo/Branding	✅ Good	"SolaceScanScout" + tagline "The Defi Oracle Meta Explorer"
Search	✅ Working	Address/tx hash/block number search
Blocks	✅ Working	View all blocks
Transactions	✅ Working	View all transactions
Bridge Monitoring	✅ Unique	CCIP bridge monitoring (differentiator)
WETH Utilities	✅ Unique	WETH wrap/unwrap tools (differentiator)
Wallet	⏳ Available	New MetaMask integration at /wallet
Responsive	✅ Good	Sticky navbar, gradient design

---

Block Production & Sync Status

Current Status (2026-01-30 21:07 UTC) — FIXED

Source	Block Number	Timestamp	Status
RPC (Chain)	1,581,086	2026-01-30 21:07 UTC	✅ Live
Explorer	1,581,090	2026-01-30 21:07:02 UTC	✅ SYNCED
Difference	+4 blocks	Real-time	✅ SYNCING

Fixed on 2026-01-30: Updated RPC endpoint from destroyed VMID 2500 (192.168.11.250) to working VMID 2201 (192.168.11.221).

Analysis

Problem: SolaceScanScout stopped indexing blocks on January 15, 2026 and has not synced since.

Impact:

• Explorer shows data that is 15 days old
• Missing 532,208 blocks of data
• Users see stale information (transactions, addresses, stats)
• Bridge monitoring and WETH utilities may show outdated data

Chain is healthy:

• RPC nodes are producing blocks normally (block 1,580,967 at 2026-01-30 21:02 UTC)
• Average block time: 2 seconds (per explorer stats API)
• Gas prices: 0.01 Gwei (low, healthy)

Explorer stats API shows:

{
  "total_blocks": "1048760",
  "total_transactions": "13156",
  "total_addresses": "94",
  "average_block_time": 2000.0,
  "gas_prices": { "slow": 0.01, "average": 0.01, "fast": 0.01 }
}

---

Root Cause Investigation

Blockscout Service Status

● blockscout.service - Blockscout Explorer
     Active: active (exited) since Sat 2026-01-24 01:00:56 PST; 6 days ago

Service is "active (exited)" — This means:

• Docker Compose started successfully
• Containers were created
• But the service itself may not be running or indexing

Last Service Restart

• Last restart: January 24, 2026 01:00 PST
• Last indexed block: January 15, 2026 16:57 UTC (9 days before restart)
• Conclusion: Restart did not resume indexing

Likely Causes

1. Blockscout container crashed/stopped after January 15
2. Database connection issue preventing indexer from running
3. RPC connection issue (Blockscout can't reach Chain 138 RPC)
4. Disk space issue on VMID 5000
5. Indexer stuck on a specific block or transaction

---

Recommendations

Immediate Actions (Critical)

1. Check Blockscout container status:

   ssh root@192.168.11.12 "pct exec 5000 -- docker ps -a | grep blockscout"
   

2. Check Blockscout logs for errors:

   ssh root@192.168.11.12 "pct exec 5000 -- docker logs blockscout --tail 200"
   

3. Check RPC connectivity from VMID 5000:

   ssh root@192.168.11.12 "pct exec 5000 -- curl -X POST http://192.168.11.250:8545 \
     -H 'Content-Type: application/json' \
     -d '{\"jsonrpc\":\"2.0\",\"method\":\"eth_blockNumber\",\"params\":[],\"id\":1}'"
   

4. Check disk space:

   ssh root@192.168.11.12 "pct exec 5000 -- df -h"
   

5. Check PostgreSQL status:

   ssh root@192.168.11.12 "pct exec 5000 -- docker logs blockscout-postgres --tail 50"
   

Fix Actions

If container stopped:

ssh root@192.168.11.12 "pct exec 5000 -- systemctl restart blockscout"

If RPC connection issue:

• Update ETHEREUM_JSONRPC_HTTP_URL in Blockscout env
• Ensure RPC endpoint is accessible from VMID 5000

If database issue:

• Check PostgreSQL logs
• Verify database not corrupted
• May need to re-index from scratch (last resort)

If indexer stuck:

• Restart Blockscout with fresh connection
• Check for specific error in logs about a problematic block/tx

---

Navigation Improvements (Optional)

Suggested Additions

1. Add "Wallet" link to live explorer navbar (currently only in Next.js version)

   • Link to /wallet for MetaMask integration
   • Icon: 🔗 or 🦊

2. Add sync status indicator to navbar

   • Show "Syncing..." or "Synced" with latest block number
   • Alert users if explorer is behind

3. Add network selector (future)

   • Switch between Chain 138, Ethereum Mainnet, ALL Mainnet
   • Useful when multi-chain support is added

4. Add dark mode toggle (UX enhancement)

   • Current design is light mode only

---

Summary

Item	Status	Priority
Navigation Bar	✅ Good	Low (working well)
Block Sync	🔴 CRITICAL	HIGH (15 days behind)
RPC Health	✅ Good	-
Blockscout Service	⚠️ Needs investigation	HIGH

Next Step: Investigate why Blockscout stopped indexing on January 15 and restart/fix the indexer.

---

Last updated: 2026-01-30
Reviewed by: AI Agent