← previous blocknext block →recent activity
Analyzing
Block #91,976,691
18 transactions · 15 stateful · 2026-07-31 17:33:41 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,976,691 · 18 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
2w07w18w29w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa366fc53…ed2a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
2 touches
0 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
2 touches
0 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: Perpl
6 conflicts on slot 0xa366fc53c7…47ed2a
Audit this contract →
← previous block·next block →recent activity