Block #73,491,420

← previous blocknext block →recent activity

Analyzing

Block #73,491,420

12 transactions · 11 stateful · 2026-05-09 16:14:20 UTC

Parallelism

42/100

Blocked

55%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,491,420  ·  12 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

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0xd976d098…ae1d

0x34b655…2a6f

12 touches
15 conflicts

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

10 touches
10 conflicts

0xedb848fe…6534

0x34b655…2a6f

8 touches
6 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 0xa91c899f02…fa6ee3

← previous block·next block →recent activity