← previous blocknext block →recent activity
Analyzing
Block #91,190,196
16 transactions · 14 stateful · 2026-07-28 23:34:46 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,190,196 · 16 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
5w07w18w210w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b2e4303…b36c
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6baed27e…26fa
0x34b655…2a6f
4 touches
1 conflict
0x6e689c48…a06b
0x34b655…2a6f
4 touches
1 conflict
0x70493b1f…7f10
0x34b655…2a6f
4 touches
1 conflict
0x72c8aeb2…9921
0x34b655…2a6f
4 touches
1 conflict
0x8b66399b…8d29
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
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 0x8b2e4303cb…feb36c
Audit this contract →
← previous block·next block →recent activity