← previous blocknext block →recent activity
Analyzing
Block #85,569,004
15 transactions · 14 stateful · 2026-07-04 15:11:51 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,569,004 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w06w17w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda46a376…f6a6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x3710478b…a791
0x34b655…2a6f
4 touches
1 conflict
0x419b2b6d…223a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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
6 conflicts on slot 0xda46a376d7…59f6a6
Audit this contract →
← previous block·next block →recent activity