← previous blocknext block →recent activity
Analyzing
Block #87,709,909
23 transactions · 21 stateful · 2026-07-14 13:35:25 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,709,909 · 23 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
1w02w13w25w06w18w09w110w011w212w314w015w117w218w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c7c65d0…0b52
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x8207c2a8…43b6
0x34b655…2a6f
8 touches
6 conflicts
0x5c591136…d322
0x34b655…2a6f
8 touches
6 conflicts
0x09cd9841…d332
0x34b655…2a6f
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0x3c7c65d0e6…a00b52
Audit this contract →
← previous block·next block →recent activity