← previous blocknext block →recent activity
Analyzing
Block #85,808,199
15 transactions · 10 stateful · 2026-07-05 17:45:57 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,808,199 · 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
6w07w18w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe496e2a…ea17
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xe02d91f7…dcdc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xfe496e2ab7…d8ea17
Audit this contract →
← previous block·next block →recent activity