← previous blocknext block →recent activity
Analyzing
Block #87,586,059
22 transactions · 18 stateful · 2026-07-13 23:47:15 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,586,059 · 22 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
8w09w110w112w213w314w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xfdcd17bb…a94a
0x34b655…2a6f
10 touches
10 conflicts
0x8b7af792…9ef0
0x34b655…2a6f
8 touches
6 conflicts
0x8ca13937…b3ce
0x34b655…2a6f
6 touches
3 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0x7c7eff13…16db
0x34b655…2a6f
6 touches
3 conflicts
0x3093e806…bde2
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity