← previous blocknext block →recent activity
Analyzing
Block #85,126,321
25 transactions · 21 stateful · 2026-07-02 14:03:34 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,126,321 · 25 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
1w02w15w09w111w212w315w016w217w018w221w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95d6e198…f79c
0x34b655…2a6f
8 touches
6 conflicts
0x3416afe1…ed59
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x73935817…e26c
0x34b655…2a6f
4 touches
1 conflict
0x742072b0…1af8
0x34b655…2a6f
4 touches
1 conflict
0x83737dd0…cc36
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 0x95d6e1989e…e0f79c
Audit this contract →
← previous block·next block →recent activity