← previous blocknext block →recent activity
Analyzing
Block #85,126,752
40 transactions · 35 stateful · 2026-07-02 14:06:27 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,126,752 · 40 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
4w05w16w27w38w49w510w011w112w213w314w428w229w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x2c506459…5351
0x34b655…2a6f
6 touches
3 conflicts
0x59645a97…3ca1
0x34b655…2a6f
6 touches
3 conflicts
0x79b3209b…f766
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x8d773511…5fd3
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity