← previous blocknext block →recent activity
Analyzing
Block #85,250,964
16 transactions · 12 stateful · 2026-07-03 03:54:00 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,250,964 · 16 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
1w02w13w26w07w110w111w212w213w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd06fb4dc…5204
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x85631114…3ff6
0xa6afd3…d132
4 touches
1 conflict
0x6cbd8def…1f53
0x34b655…2a6f
4 touches
1 conflict
0x8cc510b5…9fa8
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity