← previous blocknext block →recent activity
Analyzing
Block #95,593,102
22 transactions · 20 stateful · 2026-08-13 09:16:37 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,593,102 · 22 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
2w03w04w16w29w110w311w412w013w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf501ad8…99ed
0x34b655…2a6f
8 touches
6 conflicts
0x9a8af3c2…e4ae
0x34b655…2a6f
6 touches
3 conflicts
0x6939e474…4256
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x850def09…120b
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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
6 conflicts on slot 0xcf501ad812…7699ed
Audit this contract →
← previous block·next block →recent activity