← previous blocknext block →recent activity
Analyzing
Block #85,130,693
28 transactions · 25 stateful · 2026-07-02 14:32:48 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,130,693 · 28 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
1w02w13w24w35w47w18w09w111w012w113w014w115w216w317w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe96e3c16…a9f3
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xbc91db4e…2440
0xd32edf…ff58
9 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x676734bf…ea92
0x34b655…2a6f
8 touches
6 conflicts
0x970299b9…b0a7
0x34b655…2a6f
8 touches
6 conflicts
0xa7d27643…00fa
0x34b655…2a6f
8 touches
6 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xe96e3c16e2…cba9f3
Audit this contract →
← previous block·next block →recent activity