← previous blocknext block →recent activity
Analyzing
Block #99,276,598
24 transactions · 22 stateful · 2026-08-26 08:05:02 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,276,598 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w210w111w212w114w215w316w317w418w519w223w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa21c9a17…c000
0x34b655…2a6f
12 touches
15 conflicts
0x9d22c394…c125
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf15273a1…2c52
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xa21c9a17f3…acc000
Audit this contract →
← previous block·next block →recent activity