← previous blocknext block →recent activity
Analyzing
Block #86,921,713
19 transactions · 17 stateful · 2026-07-10 21:44:31 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,921,713 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w111w212w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd6b33e…9557
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4bd41fd9…4194
0x34b655…2a6f
4 touches
1 conflict
0x5bf44783…6166
0x34b655…2a6f
4 touches
1 conflict
0x5e4a329f…bc40
0x34b655…2a6f
4 touches
1 conflict
0x7548b289…f0dc
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x6bd6b33ee8…919557
Audit this contract →
← previous block·next block →recent activity