← previous blocknext block →recent activity
Analyzing
Block #87,489,793
20 transactions · 19 stateful · 2026-07-13 13:02:35 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,489,793 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w311w012w413w515w618w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0c0eefa8…3e5f
0x34b655…2a6f
8 touches
6 conflicts
0x0fc12355…14c4
0x34b655…2a6f
8 touches
6 conflicts
0x166182ab…8e47
0x34b655…2a6f
8 touches
6 conflicts
0x1729d844…d8e9
0x34b655…2a6f
8 touches
6 conflicts
0x22f5b72a…22e0
0x34b655…2a6f
8 touches
6 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
8 touches
6 conflicts
0x3df828b5…5a93
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity