← previous blocknext block →recent activity
Analyzing
Block #87,586,291
15 transactions · 14 stateful · 2026-07-13 23:48:48 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,586,291 · 15 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
2w03w14w25w36w49w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x6ff15a3a…da05
0x34b655…2a6f
10 touches
10 conflicts
0x36077f58…66cd
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x1716b13d…99cc
0xc8689a…ee79
6 touches
3 conflicts
0x228fc711…5bf6
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity