← previous blocknext block →recent activity
Analyzing
Block #87,614,889
21 transactions · 19 stateful · 2026-07-14 03:00:03 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,614,889 · 21 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
2w03w04w15w26w38w19w210w313w414w015w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa592dff2…81a4
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xdb7c435f…f490
0x34b655…2a6f
8 touches
6 conflicts
0x07f69062…03ec
0x34b655…2a6f
8 touches
6 conflicts
0x1d1917da…01b6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
6 touches
3 conflicts
0x68b75835…d6f3
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 0xa592dff2d3…2781a4
Audit this contract →
← previous block·next block →recent activity