← previous blocknext block →recent activity
Analyzing
Block #90,551,236
9 transactions · 7 stateful · 2026-07-26 17:59:18 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,551,236 · 9 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
3w04w15w26w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1ce9ca7…c011
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586c
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0xe75060c3…b41e
0x34b655…2a6f
4 touches
1 conflict
0xf7019ae9…bfb0
0x34b655…2a6f
4 touches
1 conflict
0x16839256…371f
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 0xb1ce9ca7e4…43c011
Audit this contract →
← previous block·next block →recent activity