← previous blocknext block →recent activity
Analyzing
Block #87,762,338
19 transactions · 19 stateful · 2026-07-14 19:26:17 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,762,338 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w410w111w212w313w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e644b16…807b
0x34b655…2a6f
10 touches
10 conflicts
0xe96e3c16…a9f3
0x34b655…2a6f
10 touches
10 conflicts
0x147259c6…1709
0x34b655…2a6f
8 touches
6 conflicts
0x72108a9f…5081
0x34b655…2a6f
8 touches
6 conflicts
0xe732567d…b65d
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xe1fe8278…8591
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
10 conflicts on slot 0x3e644b16f4…b0807b
Audit this contract →
← previous block·next block →recent activity