← previous blocknext block →recent activity
Analyzing
Block #95,163,076
17 transactions · 16 stateful · 2026-08-11 21:00:05 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,163,076 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w16w27w38w49w512w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0xb7436916…28a4
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3faf06e8…bbe7
0x34b655…2a6f
4 touches
1 conflict
0x4b54bf38…d5b6
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0xa779293bef…815e59
Audit this contract →
← previous block·next block →recent activity