← previous blocknext block →recent activity
Analyzing
Block #85,140,215
19 transactions · 17 stateful · 2026-07-02 15:36:22 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,140,215 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w18w29w310w311w016w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587911c7…9e01
0x34b655…2a6f
8 touches
6 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
8 touches
6 conflicts
0x6f8637ca…8199
0xd32edf…ff58
7 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
6 touches
3 conflicts
0xaa48195d…ffee
0x34b655…2a6f
6 touches
3 conflicts
0xab1da4f5…1c88
0x34b655…2a6f
6 touches
3 conflicts
0xcde7563a…f9fa
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x587911c74f…109e01
Audit this contract →
← previous block·next block →recent activity