← previous blocknext block →recent activity
Analyzing
Block #91,608,250
19 transactions · 17 stateful · 2026-07-30 10:40:12 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,608,250 · 19 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
4w05w17w29w311w115w016w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0x15dac349…4e37
0x34b655…2a6f
4 touches
1 conflict
0x2e546dd9…4c50
0x34b655…2a6f
4 touches
1 conflict
0x41c16dcc…78ab
0x34b655…2a6f
4 touches
1 conflict
0x73855a54…a2d2
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity