← previous blocknext block →recent activity

Analyzing

Block #73,651,769

36 transactions · 28 stateful · 2026-05-10 10:03:02 UTC

Parallelism

72/100

Blocked

57%

Avg conflicts / tx

1.64

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,651,769  ·  36 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

0x9939d2cf…a4af

0xd32edf…ff58

19 touches
45 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xe786d9a3…5c42

0x065c9d…c394

6 touches
3 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0xa3ff1ab2…8ae3

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: 0xd32edf66…9fff58

45 conflicts on slot 0x9939d2cf57…77a4af

← previous block·next block →recent activity