← previous blocknext block →recent activity
Analyzing
Block #86,634,986
18 transactions · 15 stateful · 2026-07-09 13:47:28 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,634,986 · 18 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
1w02w13w04w16w07w18w211w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x506bd3d1…bc8e
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xdc921364…4680
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x0c69433a…4f81
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
6 touches
3 conflicts
0x4c214bb3…c5d3
0x34b655…2a6f
6 touches
3 conflicts
0x583c0af9…d873
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 0x506bd3d1af…41bc8e
Audit this contract →
← previous block·next block →recent activity