← previous blocknext block →recent activity
Analyzing
Block #87,729,366
31 transactions · 29 stateful · 2026-07-14 15:45:45 UTC
Parallelism
45/100
Blocked
69%
Avg conflicts / tx
4.06
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,729,366 · 31 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
5w06w17w28w39w410w511w612w713w814w915w1016w1117w1218w1319w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xa55c4598…2988
0x34b655…2a6f
28 touches
91 conflicts
0x5b145de0…367c
0xc8689a…ee79
26 touches
78 conflicts
0x312e4698…54c0
0x34b655…2a6f
26 touches
78 conflicts
0x4ca1448c…9de6
0x34b655…2a6f
26 touches
78 conflicts
0x67905f6e…02a1
0x34b655…2a6f
26 touches
78 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
26 touches
78 conflicts
0x7e5ea60a…c4aa
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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity