← previous blocknext block →recent activity
Analyzing
Block #87,703,739
37 transactions · 33 stateful · 2026-07-14 12:54:06 UTC
Parallelism
54/100
Blocked
64%
Avg conflicts / tx
3.38
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,703,739 · 37 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
6w07w19w211w012w113w214w315w416w517w618w719w820w921w1022w1123w1225w1426w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xe1fe8278…8591
0x34b655…2a6f
14 touches
21 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
14 touches
21 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
14 touches
21 conflicts
0xe732567d…b65d
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity