← previous blocknext block →recent activity
Analyzing
Block #86,220,076
26 transactions · 26 stateful · 2026-07-07 15:33:44 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,220,076 · 26 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
1w07w08w111w013w114w016w018w119w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d1a468…dbd8
0x34b655…2a6f
6 touches
3 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
6 touches
3 conflicts
0x899a95b3…c38a
0x34b655…2a6f
6 touches
3 conflicts
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
3 conflicts on slot 0xe2d1a468cb…56dbd8
Audit this contract →
← previous block·next block →recent activity