← previous blocknext block →recent activity
Analyzing
Block #87,624,753
18 transactions · 17 stateful · 2026-07-14 04:06:00 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,624,753 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w29w010w111w112w213w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0xf386bff1…b350
0x34b655…2a6f
8 touches
6 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x91d48be7…e4e8
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity