← previous blocknext block →recent activity
Analyzing
Block #86,917,030
26 transactions · 21 stateful · 2026-07-10 21:13:11 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,917,030 · 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
1w02w16w07w18w210w211w012w114w216w317w423w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21683d77…4e07
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x195db46d…a194
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3ccc3d17…de83
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 conflicts
0x7cc0fa86…3e91
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
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
6 conflicts on slot 0x21683d77dd…434e07
Audit this contract →
← previous block·next block →recent activity