← previous blocknext block →recent activity
Analyzing
Block #90,397,188
9 transactions · 8 stateful · 2026-07-26 04:59:21 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,397,188 · 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
1w02w13w24w37w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb87dfc97…8830
0x34b655…2a6f
4 touches
1 conflict
0x07559349…89cc
0x34b655…2a6f
2 touches
0 conflicts
0x10bb4680…ebbe
0x34b655…2a6f
2 touches
0 conflicts
0x34ac5036…bedf
0x34b655…2a6f
2 touches
0 conflicts
0x540fe46f…a3d0
0x34b655…2a6f
2 touches
0 conflicts
0x59fdf55a…b42d
0x34b655…2a6f
2 touches
0 conflicts
0x745952b2…d90c
0x34b655…2a6f
2 touches
0 conflicts
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity