← previous blocknext block →recent activity
Analyzing
Block #91,025,116
16 transactions · 16 stateful · 2026-07-28 09:44:13 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,025,116 · 16 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
1w02w13w04w15w26w37w08w210w111w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85d4c7be…173a
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8ce1ffed…4889
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x98b8e5ef…bda4
0x34b655…2a6f
4 touches
1 conflict
0xa16e055b…97b8
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
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 0x85d4c7be60…63173a
Audit this contract →
← previous block·next block →recent activity