← previous blocknext block →recent activity
Analyzing
Block #86,828,089
12 transactions · 7 stateful · 2026-07-10 11:18:36 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,828,089 · 12 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
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb020c2c1…a47d
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0f4cddfd…3085
0x34b655…2a6f
4 touches
1 conflict
0x9068a9bc…86ee
0x34b655…2a6f
2 touches
0 conflicts
0xb7a47e62…7963
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity