← previous blocknext block →recent activity
Analyzing
Block #91,408,319
11 transactions · 10 stateful · 2026-07-29 17:53:23 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,408,319 · 11 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
2w03w14w05w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0x5fa03694…de10
0x34b655…2a6f
4 touches
1 conflict
0x7e7de6d7…48be
0x34b655…2a6f
4 touches
1 conflict
0x917f9a70…3764
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd4b83c55…2e87
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 0xf9e23360ff…e88ef7
Audit this contract →
← previous block·next block →recent activity