← previous blocknext block →recent activity
Analyzing
Block #87,709,106
41 transactions · 37 stateful · 2026-07-14 13:30:02 UTC
Parallelism
61/100
Blocked
65%
Avg conflicts / tx
2.22
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,709,106 · 41 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w19w211w012w113w214w315w416w517w618w719w823w227w335w1237w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x9eb155db…f714
0x34b655…2a6f
10 touches
10 conflicts
0x3a6f62be…a4e3
0x34b655…2a6f
8 touches
6 conflicts
0x3d381afb…8207
0x34b655…2a6f
8 touches
6 conflicts
0x3f53cce1…8e8f
0x34b655…2a6f
8 touches
6 conflicts
0x55cf4758…265c
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity