← previous blocknext block →recent activity
Analyzing
Block #85,354,535
67 transactions · 48 stateful · 2026-07-03 15:23:48 UTC
Parallelism
72/100
Blocked
81%
Avg conflicts / tx
3.45
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,354,535 · 67 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w09w116w219w320w221w322w423w524w627w730w833w934w1059w1161w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
34 touches
136 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
22 touches
55 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
18 touches
36 conflicts
0x1da60af2…3010
0x34b655…2a6f
18 touches
36 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
18 touches
36 conflicts
0xb624d2ea…8c87
0x34b655…2a6f
18 touches
36 conflicts
0xd99c922e…5ca0
0x34b655…2a6f
16 touches
28 conflicts
0x3230277c…ef39
0xc8689a…ee79
14 touches
21 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
136 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity