Block #73,200,613

← previous blocknext block →recent activity

Analyzing

Block #73,200,613

11 transactions · 11 stateful · 2026-05-08 07:59:27 UTC

Parallelism

55/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,200,613  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0x658b8911…82dd

0x065c9d…c394

6 touches
3 conflicts

0x72a2c989…8daa

0x065c9d…c394

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0xd2204382…283a

0x065c9d…c394

6 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

6 touches
3 conflicts

0x0175b7a6…1dbb

0x6ca43f…c331

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity