← previous blocknext block →recent activity
Analyzing
Block #87,711,437
25 transactions · 23 stateful · 2026-07-14 13:45:39 UTC
Parallelism
84/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,711,437 · 25 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
3w04w113w014w115w216w218w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6f46250b…3bf2
0x34b655…2a6f
8 touches
6 conflicts
0xb56f0740…7542
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x8616266b…025c
0x0a2fbf…29b1
4 touches
1 conflict
0xebbeecfd…c00b
0x0a2fbf…29b1
4 touches
1 conflict
0xebbeecfd…c00c
0x0a2fbf…29b1
4 touches
1 conflict
0xebbeecfd…c00d
0x0a2fbf…29b1
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity