← previous blocknext block →recent activity
Analyzing
Block #85,185,286
23 transactions · 18 stateful · 2026-07-02 20:36:31 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,185,286 · 23 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
1w02w13w04w111w012w113w214w315w417w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x056ec16c…55b9
0x34b655…2a6f
4 touches
1 conflict
0x1a4b3b89…0b51
0x34b655…2a6f
4 touches
1 conflict
0x2011ff06…05aa
0x34b655…2a6f
4 touches
1 conflict
0x3923cd2c…e6d3
0x34b655…2a6f
4 touches
1 conflict
0x41edcf35…7c0b
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x51a914cf…a822
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity