← previous blocknext block →recent activity
Analyzing
Block #87,627,086
13 transactions · 12 stateful · 2026-07-14 04:21:36 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
1.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,627,086 · 13 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
1w02w13w25w06w17w28w39w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xd44615c6…5430
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x9407f89d…82ff
0x34b655…2a6f
6 touches
3 conflicts
0x9599eb41…b5d6
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 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity