← previous blocknext block →recent activity
Analyzing
Block #85,248,386
33 transactions · 26 stateful · 2026-07-03 03:36:47 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,248,386 · 33 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
1w02w13w26w37w48w59w626w627w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22d3c767…e4d1
0x34b655…2a6f
14 touches
21 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xd2862d04…388c
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
14 touches
21 conflicts
0x7b3da897…b268
0x34b655…2a6f
14 touches
21 conflicts
0x1254087a…aa4b
0x34b655…2a6f
14 touches
21 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
21 conflicts on slot 0x22d3c767ef…68e4d1
Audit this contract →
← previous block·next block →recent activity