← previous blocknext block →recent activity
Analyzing
Block #86,665,883
25 transactions · 24 stateful · 2026-07-09 17:15:04 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,665,883 · 25 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
2w03w04w15w26w37w48w09w112w113w217w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e9a70ab…e67c
0x34b655…2a6f
10 touches
10 conflicts
0x12573732…e891
0x34b655…2a6f
10 touches
10 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x3d4584df…ffed
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
10 touches
10 conflicts
0x60c7217a…8c94
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 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 0x0e9a70abf6…d0e67c
Audit this contract →
← previous block·next block →recent activity