← previous blocknext block →recent activity
Analyzing
Block #85,178,833
14 transactions · 14 stateful · 2026-07-02 19:53:30 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,178,833 · 14 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
2w03w14w25w37w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0aa5b76b…60db
0x34b655…2a6f
6 touches
3 conflicts
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x465cad5f…fd93
0x34b655…2a6f
4 touches
1 conflict
0x4db72333…50ed
0x34b655…2a6f
4 touches
1 conflict
0x50ce3dd5…bfb4
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 0xb44564d6a3…0fbb43
Audit this contract →
← previous block·next block →recent activity