← previous blocknext block →recent activity
Analyzing
Block #87,902,477
14 transactions · 11 stateful · 2026-07-15 11:03:41 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,902,477 · 14 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
2w06w07w18w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x9f83113a…dcd8
0x34b655…2a6f
8 touches
6 conflicts
0x6323c5ea…ce8a
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0xe0ccbbee…2df8
0x34b655…2a6f
6 touches
3 conflicts
0xebe9512d…5162
0x34b655…2a6f
6 touches
3 conflicts
0xecea8d74…b45f
0x34b655…2a6f
6 touches
3 conflicts
0x7d4f656a…a3cc
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity