← previous blocknext block →recent activity
Analyzing
Block #85,131,594
40 transactions · 35 stateful · 2026-07-02 14:38:50 UTC
Parallelism
73/100
Blocked
77%
Avg conflicts / tx
2.13
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,131,594 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w09w112w013w121w222w423w524w627w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3c7520fc…9ca3
0x34b655…2a6f
8 touches
6 conflicts
0x9495bffc…46e6
0x34b655…2a6f
6 touches
5 conflicts
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity