← previous blocknext block →recent activity
Analyzing
Block #87,705,067
50 transactions · 40 stateful · 2026-07-14 13:03:00 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
2.38
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,705,067 · 50 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w07w09w119w020w121w222w323w424w525w626w727w828w929w1030w1132w433w1235w136w237w1438w342w443w547w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x4560e5a8…b741
0x34b655…2a6f
12 touches
15 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x7837c02d…0965
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity