← previous blocknext block →recent activity
Analyzing
Block #87,629,260
56 transactions · 47 stateful · 2026-07-14 04:36:10 UTC
Parallelism
66/100
Blocked
81%
Avg conflicts / tx
4.11
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,629,260 · 56 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
1w02w03w16w28w09w110w011w112w113w014w115w216w317w418w541w1742w143w244w345w446w548w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
36 touches
153 conflicts
0x08330b36…ae29
0x34b655…2a6f
22 touches
55 conflicts
0x49f75237…44f4
0x34b655…2a6f
20 touches
45 conflicts
0x5b145de0…367c
0xc8689a…ee79
20 touches
45 conflicts
0x2697123c…8526
0x34b655…2a6f
20 touches
45 conflicts
0x7bc81c3e…54a2
0x34b655…2a6f
20 touches
45 conflicts
0x8d68898d…ab1d
0x34b655…2a6f
20 touches
45 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
20 touches
45 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
153 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity