← previous blocknext block →recent activity
Analyzing
Block #86,628,931
29 transactions · 22 stateful · 2026-07-09 13:06:56 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,628,931 · 29 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
1w02w13w24w38w09w010w011w112w213w114w415w217w019w320w122w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x011a7c33…70ec
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xcbf8175e…ac27
0x065c9d…c394
6 touches
3 conflicts
0x421c32c1…4629
0x754704…b603
6 touches
3 conflicts
0x5a1cd68f…4125
0x754704…b603
6 touches
3 conflicts
0x6609dc6a…a0ec
0x754704…b603
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity