← previous blocknext block →recent activity
Analyzing
Block #90,240,354
20 transactions · 18 stateful · 2026-07-25 15:40:35 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,240,354 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w09w110w112w213w314w015w117w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x33fb94b9…d3ae
0x34b655…2a6f
4 touches
1 conflict
0xf321dfbc…68dc
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c848
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c849
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity