← previous blocknext block →recent activity
Analyzing
Block #90,456,942
11 transactions · 10 stateful · 2026-07-26 10:04:57 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,456,942 · 11 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
1w04w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xd4498307…88dc
0x34b655…2a6f
6 touches
3 conflicts
0xfd196940…c22d
0x34b655…2a6f
4 touches
1 conflict
0xcf0f3352…1fd9
0x34b655…2a6f
4 touches
1 conflict
0xdbdcdc19…6f8f
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbde
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbdf
0x34b655…2a6f
4 touches
1 conflict
0x6c084dcb…640c
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity