← previous blocknext block →recent activity
Analyzing
Block #85,178,313
83 transactions · 55 stateful · 2026-07-02 19:50:02 UTC
Parallelism
76/100
Blocked
69%
Avg conflicts / tx
2.42
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,178,313 · 83 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
1w06w113w214w315w416w520w525w226w329w439w640w641w766w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x23ecca82…3cde
0xd32edf…ff58
13 touches
21 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
12 touches
15 conflicts
0xd06fb4dc…5204
0x34b655…2a6f
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
12 touches
15 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
12 touches
15 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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity