← previous blocknext block →recent activity
Analyzing
Block #85,181,140
23 transactions · 22 stateful · 2026-07-02 20:08:53 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,181,140 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w08w112w213w114w319w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b111712…0e59
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0aa5b76b…60db
0x34b655…2a6f
6 touches
3 conflicts
0x11431f9d…42c5
0x34b655…2a6f
6 touches
3 conflicts
0x6f2cf408…3432
0x34b655…2a6f
6 touches
3 conflicts
0x765cd07a…1018
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
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 0x2b1117126f…080e59
Audit this contract →
← previous block·next block →recent activity