← previous blocknext block →recent activity

Analyzing

Block #73,923,932

33 transactions · 29 stateful · 2026-05-11 16:29:07 UTC

Parallelism

67/100

Blocked

66%

Avg conflicts / tx

2.09

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,923,932  ·  33 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x5de96bd3…c60c

0x34b655…2a6f

16 touches
28 conflicts

0x5d70606a…1d53

0x34b655…2a6f

14 touches
21 conflicts

0xef3e6db1…49e9

0x34b655…2a6f

14 touches
21 conflicts

0xb142d1c0…fe1e

0x34b655…2a6f

14 touches
21 conflicts

0xac8e97a0…8426

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

12 touches
15 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: 0x34b6552d…112a6f

28 conflicts on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity