← previous blocknext block →recent activity
Analyzing
Block #91,255,148
23 transactions · 22 stateful · 2026-07-29 05:01:35 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,255,148 · 23 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
1w02w13w06w07w08w110w212w113w114w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
6 touches
3 conflicts
0xbabe821d…939b
0x34b655…2a6f
4 touches
1 conflict
0xc1ce7480…b2cc
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 0x91b0f8edc5…b76bd7
Audit this contract →
← previous block·next block →recent activity