← previous blocknext block →recent activity
Analyzing
Block #87,662,022
28 transactions · 24 stateful · 2026-07-14 08:15:03 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,662,022 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w011w115w216w318w019w121w122w223w225w427w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x648bb928…97f2
0x34b655…2a6f
10 touches
10 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0x87ad6992…9735
0x34b655…2a6f
6 touches
3 conflicts
0x91ace65b…97af
0x34b655…2a6f
6 touches
3 conflicts
0xe2513f8c…b81d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x0733be30…112f
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
10 conflicts on slot 0x648bb9281b…e597f2
Audit this contract →
← previous block·next block →recent activity