← previous blocknext block →recent activity
Analyzing
Block #85,190,800
22 transactions · 21 stateful · 2026-07-02 21:13:12 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,190,800 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w418w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x06aed19e…ca57
0x34b655…2a6f
8 touches
6 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 conflicts
0x8e507257…71c1
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xa9ad4c70…1120
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity