← previous blocknext block →recent activity
Analyzing
Block #95,034,098
14 transactions · 13 stateful · 2026-08-11 10:10:51 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,034,098 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a2a0532…f8b1
0x968279…9342
10 touches
10 conflicts
0x9a2a0532…f8b3
0x968279…9342
10 touches
10 conflicts
0xe05789d9…236f
0x968279…9342
10 touches
10 conflicts
0xe05789d9…2370
0x968279…9342
10 touches
10 conflicts
0xe05789d9…2373
0x968279…9342
10 touches
10 conflicts
0xe05789d9…2374
0x968279…9342
10 touches
10 conflicts
0xe05789d9…2376
0x968279…9342
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x96827978…f09342
10 conflicts on slot 0x9a2a0532c5…fdf8b1
Audit this contract →
← previous block·next block →recent activity