← previous blocknext block →recent activity
Analyzing
Block #87,616,361
24 transactions · 21 stateful · 2026-07-14 03:09:54 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,616,361 · 24 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
1w02w15w06w07w19w010w111w212w313w417w218w119w521w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xa435dee8…f2be
0x34b655…2a6f
8 touches
6 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0x262a4cd6…9d3c
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x64687417…8d60
0x34b655…2a6f
4 touches
1 conflict
0x6a211cb8…a7ce
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity