← previous blocknext block →recent activity

Analyzing

Block #92,804,951

17 transactions · 16 stateful · 2026-08-03 15:00:37 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,804,951  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x17ea6399…65cc

0x968279…9342

8 touches
6 conflicts

0x17ea6399…65ce

0x968279…9342

8 touches
6 conflicts

0x6940e8d6…b534

0x968279…9342

8 touches
6 conflicts

0x6940e8d6…b535

0x968279…9342

8 touches
6 conflicts

0x6940e8d6…b538

0x968279…9342

8 touches
6 conflicts

0x6940e8d6…b539

0x968279…9342

8 touches
6 conflicts

0x6940e8d6…b53b

0x968279…9342

8 touches
6 conflicts

0xca841faa…486a

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: 0x96827978…f09342

6 conflicts on slot 0x17ea639950…fd65cc

← previous block·next block →recent activity