← previous blocknext block →recent activity
Analyzing
Block #87,700,214
119 transactions · 62 stateful · 2026-07-14 12:30:20 UTC
Parallelism
82/100
Blocked
81%
Avg conflicts / tx
2.89
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,700,214 · 119 txs across 21 waves · depth 21
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
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w48w510w635w937w1039w1248w1349w1756w1857w1958w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0xd900bc9e…9239
0xd32edf…ff58
29 touches
105 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
24 touches
66 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
24 touches
66 conflicts
0x5170a218…3a84
0xc8689a…ee79
24 touches
66 conflicts
0x2fdfa032…139c
0x34b655…2a6f
24 touches
66 conflicts
0x55cf4758…265c
0x34b655…2a6f
24 touches
66 conflicts
0xdbb43016…7cc4
0x34b655…2a6f
24 touches
66 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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity