← previous blocknext block →recent activity
Analyzing
Block #85,134,772
20 transactions · 19 stateful · 2026-07-02 15:00:01 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,134,772 · 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
1w02w13w25w313w415w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc99e7125…81b1
0x34b655…2a6f
5 touches
3 conflicts
0x5f8acc70…8c84
0x34b655…2a6f
4 touches
1 conflict
0x1d521b7f…b009
0x34b655…2a6f
4 touches
1 conflict
0x2549dda6…9e24
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
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: 0x681e908b…e1ae09
10 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity