← previous blocknext block →recent activity

Analyzing

Block #73,807,292

11 transactions · 9 stateful · 2026-05-11 03:32:09 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,807,292  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x0fa5e7bf…a4da

0x34b655…2a6f

6 touches
3 conflicts

0x129ba946…48ab

0x34b655…2a6f

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

6 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

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

3 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity