← previous blocknext block →recent activity
Analyzing
Block #85,157,290
24 transactions · 21 stateful · 2026-07-02 17:30:11 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,157,290 · 24 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
1w04w06w07w18w012w016w117w120w221w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x274b85f7…c526
0x34b655…2a6f
8 touches
6 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x63b15849…80b2
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x84df646f…8816
0x34b655…2a6f
4 touches
1 conflict
0x97fe3267…5e87
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
6 conflicts on slot 0x274b85f751…f5c526
Audit this contract →
← previous block·next block →recent activity