← previous blocknext block →recent activity
Analyzing
Block #85,138,821
34 transactions · 27 stateful · 2026-07-02 15:27:03 UTC
Parallelism
53/100
Blocked
67%
Avg conflicts / tx
2.03
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #85,138,821 · 34 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w212w313w414w515w616w717w819w222w127w928w1029w1130w1232w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
10 touches
10 conflicts
0x37421b44…45b5
0x34b655…2a6f
6 touches
3 conflicts
0x43e2eda1…396f
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x5a19ef35…dc70
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