← previous blocknext block →recent activity
Analyzing
Block #87,700,507
55 transactions · 47 stateful · 2026-07-14 12:32:20 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
3
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,700,507 · 55 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w39w410w311w517w419w020w121w222w323w424w542w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x2fdfa032…139c
0x34b655…2a6f
14 touches
21 conflicts
0xdbb43016…7cc4
0x34b655…2a6f
14 touches
21 conflicts
0x521f03f8…dc0e
0x34b655…2a6f
14 touches
21 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
14 touches
21 conflicts
0x55cf4758…265c
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity