← previous blocknext block →recent activity
Analyzing
Block #86,660,882
21 transactions · 18 stateful · 2026-07-09 16:41:44 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,660,882 · 21 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
6 touches
3 conflicts
0x0d0d2659…e1f2
0x34b655…2a6f
6 touches
3 conflicts
0x1ae9c44b…e801
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x660c9d95…7859
0x34b655…2a6f
4 touches
1 conflict
0x76d36fa4…aaf6
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity