← previous blocknext block →recent activity
Analyzing
Block #87,664,630
17 transactions · 15 stateful · 2026-07-14 08:32:30 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,664,630 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w511w312w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2981b6be…7be0
0x34b655…2a6f
6 touches
3 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x183c10a3…2e0a
0x34b655…2a6f
4 touches
1 conflict
0x1a017137…af9f
0x34b655…2a6f
4 touches
1 conflict
0x1b39afc7…4e44
0x34b655…2a6f
4 touches
1 conflict
0x1b5f5a50…c006
0x34b655…2a6f
4 touches
1 conflict
0x1fa4321c…4f31
0x34b655…2a6f
4 touches
1 conflict
0x1ffbc5c9…461f
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x2981b6be99…7e7be0
Audit this contract →
← previous block·next block →recent activity