← previous blocknext block →recent activity
Analyzing
Block #86,249,969
26 transactions · 23 stateful · 2026-07-07 18:53:27 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,249,969 · 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
3w04w06w110w211w013w117w319w423w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x6cc1a133…89a0
0x40c49f…2af0
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x6b25c3c6…bf3f
0x34b655…2a6f
4 touches
1 conflict
0x809368b3…07bc
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity