← previous blocknext block →recent activity
Analyzing
Block #91,100,652
20 transactions · 16 stateful · 2026-07-28 16:04:19 UTC
Parallelism
85/100
Blocked
19%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,100,652 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w111w212w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70a7b5d6…fe0e
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0x154b56c6…3d64
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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 0x70a7b5d69a…6cfe0e
Audit this contract →
← previous block·next block →recent activity