← previous blocknext block →recent activity
Analyzing
Block #85,138,570
21 transactions · 20 stateful · 2026-07-02 15:25:23 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,138,570 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w412w514w116w017w118w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x0d32a433…9e53
0x34b655…2a6f
8 touches
6 conflicts
0x366f651e…6100
0x34b655…2a6f
8 touches
6 conflicts
0x0542cd09…3389
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
8 touches
6 conflicts
0xaa48195d…ffee
0x34b655…2a6f
8 touches
6 conflicts
0xb3e0e8ea…b4e1
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity