← previous blocknext block →recent activity
Analyzing
Block #85,983,844
16 transactions · 12 stateful · 2026-07-06 13:16:35 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,983,844 · 16 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
1w02w13w04w05w17w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0x9b7cf16a…5903
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xf9f0d63a…2142
0x40c49f…2af0
4 touches
1 conflict
0x89f9ec96…59e8
0xd32edf…ff58
3 touches
1 conflict
0x58b4a301…36b8
0x065c9d…c394
2 touches
0 conflicts
0x8c75dd93…885d
0x065c9d…c394
2 touches
0 conflicts
0x9fdb9730…e8e5
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity