← previous blocknext block →recent activity
Analyzing
Block #85,166,675
18 transactions · 17 stateful · 2026-07-02 18:32:32 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,166,675 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w29w310w111w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x754c7f04…5673
0x34b655…2a6f
6 touches
3 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xa02b1560…9801
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x754c7f0456…785673
Audit this contract →
← previous block·next block →recent activity