Block #73,922,842

← previous blocknext block →recent activity

Analyzing

Block #73,922,842

14 transactions · 12 stateful · 2026-05-11 16:21:51 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,922,842  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xee230b20…5a0f

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

10 touches
10 conflicts

0x9d652ee8…83ca

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0x9be2b99a…a959

0x34b655…2a6f

6 touches
3 conflicts

0xac8e97a0…8426

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

15 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity