← previous blocknext block →recent activity
Analyzing
Block #95,034,077
17 transactions · 16 stateful · 2026-08-11 10:10:44 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,034,077 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w014w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a2a0532…f8b3
0x968279…9342
8 touches
6 conflicts
0xe05789d9…236f
0x968279…9342
8 touches
6 conflicts
0xe05789d9…2370
0x968279…9342
8 touches
6 conflicts
0xe05789d9…2373
0x968279…9342
8 touches
6 conflicts
0xe05789d9…2374
0x968279…9342
8 touches
6 conflicts
0xe05789d9…2376
0x968279…9342
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x9a2a0532…f8b0
0x968279…9342
8 touches
6 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
6 conflicts on slot 0x9a2a0532c5…fdf8b3
Audit this contract →
← previous block·next block →recent activity