← previous blocknext block →recent activity

Analyzing

Block #73,920,922

43 transactions · 29 stateful · 2026-05-11 16:09:06 UTC

Parallelism

77/100

Blocked

69%

Avg conflicts / tx

1.47

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,920,922  ·  43 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2bc7022a…756d

0xd32edf…ff58

17 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x03df3a18…58e7

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

8 touches
6 conflicts

0xee230b20…5a0f

0x34b655…2a6f

8 touches
6 conflicts

0x1319ae2c…7f9a

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

36 conflicts on slot 0x2bc7022a40…ad756d

← previous block·next block →recent activity