← previous blocknext block →recent activity
Analyzing
Block #85,135,847
20 transactions · 20 stateful · 2026-07-02 15:07:12 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,135,847 · 20 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
2w03w15w06w07w110w011w212w214w115w117w018w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x379a09c4…259b
0x34b655…2a6f
6 touches
3 conflicts
0x366f651e…6100
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6ca32a09…4e48
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
0x34b655…2a6f
4 touches
1 conflict
0x8c0a0eea…8d2d
0x34b655…2a6f
4 touches
1 conflict
0xa1111a1a…f235
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x379a09c457…4e259b
Audit this contract →
← previous block·next block →recent activity