← previous blocknext block →recent activity
Analyzing
Block #85,100,654
36 transactions · 35 stateful · 2026-07-02 11:11:36 UTC
Parallelism
53/100
Blocked
69%
Avg conflicts / tx
3.08
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #85,100,654 · 36 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w39w111w012w113w214w315w416w517w618w719w820w921w1022w1124w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xe89cdd8c…69e7
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0xa3d58191…1c49
0x34b655…2a6f
16 touches
28 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
16 touches
28 conflicts
0xc1647db7…f853
0x34b655…2a6f
16 touches
28 conflicts
0xc83310b1…c778
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity