← previous blocknext block →recent activity
Analyzing
Block #86,904,133
19 transactions · 17 stateful · 2026-07-10 19:47:02 UTC
Parallelism
63/100
Blocked
35%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,904,133 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
10 touches
10 conflicts
0x3522af60…d679
0x34b655…2a6f
6 touches
3 conflicts
0x650e90b3…213c
0x34b655…2a6f
6 touches
3 conflicts
0x650e90b3…213d
0x34b655…2a6f
6 touches
3 conflicts
0x7accd167…4103
0x34b655…2a6f
6 touches
3 conflicts
0x8dfef5ae…9361
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity