← previous blocknext block →recent activity
Analyzing
Block #90,786,742
20 transactions · 19 stateful · 2026-07-27 13:44:03 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,786,742 · 20 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
1w02w13w06w07w18w09w110w111w212w013w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x281e160c…fdf2
0x34b655…2a6f
6 touches
3 conflicts
0x37674bd8…8f35
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x850b60c9…1b4a
0x34b655…2a6f
4 touches
1 conflict
0x97c66e1e…8c97
0x34b655…2a6f
4 touches
1 conflict
0xb91b392c…52bb
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity