← previous blocknext block →recent activity
Analyzing
Block #87,419,232
20 transactions · 17 stateful · 2026-07-13 05:10:49 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,419,232 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w16w27w38w410w511w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e27bdfb…108a
0x34b655…2a6f
14 touches
21 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x21aca45f…3e3a
0x34b655…2a6f
6 touches
3 conflicts
0x3ddc7c81…6214
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4b0a67ef…b8ba
0x34b655…2a6f
6 touches
3 conflicts
0x5b93c1fa…eac7
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 0x6e27bdfb04…5c108a
Audit this contract →
← previous block·next block →recent activity