← previous blocknext block →recent activity
Analyzing
Block #87,723,226
42 transactions · 37 stateful · 2026-07-14 15:04:39 UTC
Parallelism
62/100
Blocked
68%
Avg conflicts / tx
3.12
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,723,226 · 42 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
2w03w04w16w07w18w19w010w113w014w115w216w317w418w519w620w721w822w923w1024w1126w927w133w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7525206c…fbd5
0x34b655…2a6f
10 touches
10 conflicts
0xfed09e59…a493
0x34b655…2a6f
8 touches
6 conflicts
0x19b6aaea…01c3
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity