← previous blocknext block →recent activity
Analyzing
Block #85,180,338
16 transactions · 15 stateful · 2026-07-02 20:03:31 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,180,338 · 16 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
1w02w14w05w16w27w311w112w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdd7f0a5…d417
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x1b95af74…d320
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xffb8950c…23c6
0x34b655…2a6f
6 touches
3 conflicts
0xb6fa5378…559c
0x34b655…2a6f
6 touches
3 conflicts
0x2011ff06…05aa
0x34b655…2a6f
6 touches
3 conflicts
0xa405bf23…e482
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 0xcdd7f0a502…4ed417
Audit this contract →
← previous block·next block →recent activity