← previous blocknext block →recent activity
Analyzing
Block #87,702,907
37 transactions · 33 stateful · 2026-07-14 12:48:29 UTC
Parallelism
57/100
Blocked
64%
Avg conflicts / tx
1.95
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,702,907 · 37 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w09w110w211w312w413w514w615w721w123w826w1127w328w433w1236w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x5170a218…3a84
0xc8689a…ee79
12 touches
15 conflicts
0xe1fe8278…8591
0x34b655…2a6f
12 touches
15 conflicts
0xe732567d…b65d
0x34b655…2a6f
12 touches
15 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0x8ff3d491…6b55
0x34b655…2a6f
10 touches
10 conflicts
0x5c591136…d322
0x34b655…2a6f
10 touches
10 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity