← previous blocknext block →recent activity
Analyzing
Block #85,124,231
26 transactions · 19 stateful · 2026-07-02 13:49:35 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,124,231 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w013w114w217w218w121w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22d3c767…e4d1
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
4 touches
1 conflict
0x3f8464ec…052c
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x656bd53e…af4e
0x34b655…2a6f
4 touches
1 conflict
0x7fcfe8d7…c1cd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x22d3c767ef…68e4d1
Audit this contract →
← previous block·next block →recent activity