Block #73,748,933

← previous blocknext block →recent activity

Analyzing

Block #73,748,933

18 transactions · 14 stateful · 2026-05-10 20:58:43 UTC

Parallelism

50/100

Blocked

57%

Avg conflicts / tx

1.56

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,748,933  ·  18 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

0xa91c899f…6ee3

0x34b655…2a6f

14 touches
21 conflicts

0x9753c6ec…6479

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfac43f12…b842

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

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

21 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity