← previous blocknext block →recent activity
Analyzing
Block #86,511,853
19 transactions · 17 stateful · 2026-07-09 00:02:46 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,511,853 · 19 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
3w04w05w19w110w211w312w213w114w315w316w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba559de1…6d2c
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
6 touches
3 conflicts
0xe12ecbaf…0e17
0x34b655…2a6f
6 touches
3 conflicts
0xe9dc0500…0df3
0x34b655…2a6f
6 touches
3 conflicts
0xefcdf197…96a2
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 0xba559de17c…336d2c
Audit this contract →
← previous block·next block →recent activity