← previous blocknext block →recent activity

Analyzing

Block #73,664,281

16 transactions · 14 stateful · 2026-05-10 11:27:22 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,664,281  ·  16 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

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0xee300eeb…4488

0x34b655…2a6f

6 touches
3 conflicts

0x6c4fa36f…769f

0x065c9d…c394

5 touches
3 conflicts

0x7d77e413…f98c

0x065c9d…c394

5 touches
3 conflicts

0xc6cddf74…4882

0x065c9d…c394

5 touches
3 conflicts

0x1a4b4152…0a08

0x6c4bfa…a540

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

3 conflicts on slot 0x7f81fb82c1…ec633e

← previous block·next block →recent activity