← previous blocknext block →recent activity
Analyzing
Block #87,595,891
52 transactions · 40 stateful · 2026-07-14 00:53:01 UTC
Parallelism
71/100
Blocked
73%
Avg conflicts / tx
2.63
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,595,891 · 52 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w110w011w112w218w119w223w530w431w632w733w834w136w937w1039w240w341w442w543w644w647w1148w1250w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x4b628349…f327
0x34b655…2a6f
12 touches
15 conflicts
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity