← previous blocknext block →recent activity
Analyzing
Block #85,167,073
17 transactions · 15 stateful · 2026-07-02 18:35:10 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,167,073 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w414w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x16b3a441…13db
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
6 touches
3 conflicts
0xa457c06e…2f06
0x34b655…2a6f
6 touches
3 conflicts
0xb251976b…4938
0x34b655…2a6f
6 touches
3 conflicts
0xd25a34fd…3e4d
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity