← previous blocknext block →recent activity
Analyzing
Block #86,678,189
23 transactions · 22 stateful · 2026-07-09 18:37:12 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,678,189 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w411w512w613w716w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1647db7…f853
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x250c8181…eef2
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x485ae99d…f26f
0x34b655…2a6f
8 touches
6 conflicts
0x4e460439…5ba2
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
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 0xc1647db712…42f853
Audit this contract →
← previous block·next block →recent activity