← previous blocknext block →recent activity
Analyzing
Block #85,352,079
70 transactions · 50 stateful · 2026-07-03 15:07:29 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
2.39
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,352,079 · 70 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w18w210w311w012w113w216w317w451w152w455w256w358w559w660w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
10 touches
10 conflicts
0xefcdf197…96a2
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity