← previous blocknext block →recent activity
Analyzing
Block #87,642,172
48 transactions · 38 stateful · 2026-07-14 06:02:26 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.98
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,642,172 · 48 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w08w110w111w012w113w214w315w416w517w624w625w731w832w934w135w1036w242w1143w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x948e8d20…a8df
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x00d60c65…745d
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity