← previous blocknext block →recent activity
Analyzing
Block #85,146,986
19 transactions · 17 stateful · 2026-07-02 16:21:31 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,146,986 · 19 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
1w02w13w26w09w110w211w313w316w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x5b353877…605d
0x34b655…2a6f
8 touches
6 conflicts
0x26b356be…072b
0x34b655…2a6f
8 touches
6 conflicts
0xc23dff7c…33f4
0xd32edf…ff58
7 touches
6 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xfe9f6d52…b2a1
0x34b655…2a6f
6 touches
3 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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity