← previous blocknext block →recent activity
Analyzing
Block #87,498,304
20 transactions · 18 stateful · 2026-07-13 13:59:32 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,498,304 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w29w014w315w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x9692085a…b7be
0x34b655…2a6f
6 touches
3 conflicts
0x369883e3…a449
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x158becdc…73ed
0x34b655…2a6f
4 touches
1 conflict
0x1e6e9104…f143
0x34b655…2a6f
4 touches
1 conflict
0x27b9caf2…c102
0x34b655…2a6f
4 touches
1 conflict
0x3e0072a8…95fc
0x34b655…2a6f
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity