← previous blocknext block →recent activity
Analyzing
Block #85,133,341
22 transactions · 22 stateful · 2026-07-02 14:50:30 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,133,341 · 22 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
1w04w05w16w27w38w49w512w513w615w116w219w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xd6418d68…bdc5
0x34b655…2a6f
8 touches
6 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
8 touches
6 conflicts
0xe47478a3…a058
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xd6fbd59c…2646
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity