← previous blocknext block →recent activity
Analyzing
Block #87,063,305
20 transactions · 18 stateful · 2026-07-11 13:30:34 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,063,305 · 20 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
2w07w18w29w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe613a978…22a4
0x34b655…2a6f
8 touches
6 conflicts
0xee06e767…00d6
0x34b655…2a6f
4 touches
1 conflict
0xb367dbbf…adda
0x34b655…2a6f
4 touches
1 conflict
0xc00a2fde…914f
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xe684760e…ece0
0x34b655…2a6f
4 touches
1 conflict
0x034d14da…9f5f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0xe613a9789a…5022a4
Audit this contract →
← previous block·next block →recent activity