← previous blocknext block →recent activity
Analyzing
Block #85,509,083
10 transactions · 9 stateful · 2026-07-04 08:32:51 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,509,083 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9aff966c…53ce
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb838bbe6…2931
0x34b655…2a6f
6 touches
3 conflicts
0xef8649cd…8ebc
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x46c7aa11…f04f
0x34b655…2a6f
4 touches
1 conflict
0x4cb46981…9f95
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0x9aff966cb5…3153ce
Audit this contract →
← previous block·next block →recent activity