← previous blocknext block →recent activity

Analyzing

Block #73,679,254

29 transactions · 23 stateful · 2026-05-10 13:08:36 UTC

Parallelism

69/100

Blocked

70%

Avg conflicts / tx

2.38

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,679,254  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xa8368f3a…b822

0xd32edf…ff58

17 touches
36 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

14 touches
21 conflicts

0xc6f91b2f…b30f

0x34b655…2a6f

14 touches
21 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

12 touches
15 conflicts

0x908d4442…2c4b

0x34b655…2a6f

12 touches
15 conflicts

0xb8bb189d…67df

0x34b655…2a6f

10 touches
10 conflicts

0xd49762c9…1359

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: 0xd32edf66…9fff58

36 conflicts on slot 0xa8368f3ab1…bbb822

← previous block·next block →recent activity