← previous blocknext block →recent activity

Analyzing

Block #99,990,025

24 transactions · 23 stateful · 2026-08-28 20:10:10 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,990,025  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x0dd3d3cd…7281

0x34b655…2a6f

6 touches
3 conflicts

0x6aa2827e…9709

0x34b655…2a6f

6 touches
3 conflicts

0xf783b156…d2f6

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x5655f5c3…6b75

0x34b655…2a6f

4 touches
1 conflict

0x627738d1…db02

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x0dd3d3cd18…c87281

← previous block·next block →recent activity