← previous blocknext block →recent activity
Analyzing
Block #85,274,083
15 transactions · 14 stateful · 2026-07-03 06:27:56 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,274,083 · 15 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
1w02w13w05w19w211w012w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
8 touches
6 conflicts
0xe9564b38…d865
0x34b655…2a6f
6 touches
3 conflicts
0xc57747c0…99d1
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x0dbf9688…c6cf
0x103222…7496
4 touches
1 conflict
0xbb6b5cc3…4c49
0x103222…7496
4 touches
1 conflict
0xc52373dd…36b7
0x188d58…ea8e
4 touches
1 conflict
0xc52373dd…36b8
0x188d58…ea8e
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
6 conflicts on slot 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity