← previous blocknext block →recent activity
Analyzing
Block #91,128,124
28 transactions · 23 stateful · 2026-07-28 18:22:30 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,128,124 · 28 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
2w04w06w18w013w117w018w120w221w322w424w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0x00cba8ba…84a6
0x34b655…2a6f
6 touches
3 conflicts
0xc7e7500d…4a4f
0x34b655…2a6f
4 touches
1 conflict
0xccb98db5…ae19
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
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 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity