← previous blocknext block →recent activity
Analyzing
Block #86,904,812
14 transactions · 11 stateful · 2026-07-10 19:51:35 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,904,812 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9d64d7f8…ce93
0x34b655…2a6f
4 touches
1 conflict
0x8dfef5ae…9361
0x34b655…2a6f
4 touches
1 conflict
0x8f7038d3…3804
0x34b655…2a6f
2 touches
0 conflicts
0x94b8e9d6…77d6
0x34b655…2a6f
2 touches
0 conflicts
0xe4b8f2c5…f54d
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity