Block #73,374,945

← previous blocknext block →recent activity

Analyzing

Block #73,374,945

10 transactions · 10 stateful · 2026-05-09 03:19:11 UTC

Parallelism

40/100

Blocked

50%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,374,945  ·  10 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x5ac8e7ad…c382

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xcdf2341b…575c

0x065c9d…c394

5 touches
3 conflicts

0x06161458…e6eb

0x065c9d…c394

3 touches
1 conflict

0x386f69ff…f50b

0x065c9d…c394

3 touches
1 conflict

0x6b1d8759…c965

0x065c9d…c394

3 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity