← previous blocknext block →recent activity
Analyzing
Block #91,104,741
14 transactions · 13 stateful · 2026-07-28 16:24:53 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,104,741 · 14 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
2w03w06w17w28w310w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…7215
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7223
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc8d08709…580b
0x34b655…2a6f
6 touches
3 conflicts
0x6cad9553…19d1
0x34b655…2a6f
6 touches
3 conflicts
0x1466e362…3849
0x34b655…2a6f
6 touches
3 conflicts
0x756fae9d…8875
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xac2a02739b…817215
Audit this contract →
← previous block·next block →recent activity