← previous blocknext block →recent activity
Analyzing
Block #87,753,068
16 transactions · 16 stateful · 2026-07-14 18:24:18 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,753,068 · 16 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
1w04w05w16w27w38w410w011w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed8057f7…bf53
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x98afad44…850d
0x34b655…2a6f
10 touches
10 conflicts
0xa03dff75…cbf0
0x34b655…2a6f
10 touches
10 conflicts
0xc264135b…ac7f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
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
10 conflicts on slot 0xed8057f71f…b4bf53
Audit this contract →
← previous block·next block →recent activity