← previous blocknext block →recent activity
Analyzing
Block #85,810,955
14 transactions · 11 stateful · 2026-07-05 18:04:18 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,810,955 · 14 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
3w06w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6aabe89…92f5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x4687571a…7681
0x34b655…2a6f
4 touches
1 conflict
0x472b4646…deb0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
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
3 conflicts on slot 0xd6aabe893a…bf92f5
Audit this contract →
← previous block·next block →recent activity