← previous blocknext block →recent activity

Analyzing

Block #73,273,970

29 transactions · 22 stateful · 2026-05-08 16:07:23 UTC

Parallelism

86/100

Blocked

45%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,273,970  ·  29 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity