← previous blocknext block →recent activity
Analyzing
Block #87,723,327
26 transactions · 25 stateful · 2026-07-14 15:05:20 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,723,327 · 26 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
1w02w13w04w15w06w18w210w211w315w416w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x50718952…7c75
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x4cee015b…1a5e
0x34b655…2a6f
8 touches
6 conflicts
0x80fd3987…2314
0x34b655…2a6f
8 touches
6 conflicts
0x255ba9f3…396d
0x34b655…2a6f
8 touches
6 conflicts
0x36890fff…f3d1
0x34b655…2a6f
8 touches
6 conflicts
0xcf5ef070…7d4f
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
10 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity