← previous blocknext block →recent activity
Analyzing
Block #87,900,068
22 transactions · 21 stateful · 2026-07-15 10:47:34 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,900,068 · 22 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
3w04w110w111w212w313w015w416w117w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xe40c96f3…9ce4
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x09dddc76…e12a
0x34b655…2a6f
6 touches
3 conflicts
0x50718952…7c75
0x34b655…2a6f
6 touches
3 conflicts
0x7ba216b2…eec1
0x34b655…2a6f
6 touches
3 conflicts
0x7ba216b2…eec2
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity