← previous blocknext block →recent activity

Analyzing

Block #73,389,919

24 transactions · 22 stateful · 2026-05-09 04:58:45 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

1.96

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,389,919  ·  24 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

0xc6417de0…2191

0xc8689a…ee79

18 touches
36 conflicts

0x57de3828…3fbb

0x34b655…2a6f

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0x908d4442…2c4b

0x34b655…2a6f

18 touches
36 conflicts

0x99f080dc…58c1

0x34b655…2a6f

18 touches
36 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

18 touches
36 conflicts

0xedb848fe…6534

0x34b655…2a6f

18 touches
36 conflicts

0xd49762c9…1359

0x34b655…2a6f

16 touches
28 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: 0xc8689a47…62ee79

36 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity