Block #73,211,537

← previous blocknext block →recent activity

Analyzing

Block #73,211,537

16 transactions · 13 stateful · 2026-05-08 09:12:04 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,211,537  ·  16 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

0x554f1ada…6916

0x6ca43f…c331

6 touches
3 conflicts

0x70b2f813…783c

0x2a68ba…90c5

6 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

6 touches
3 conflicts

0x00000000…000b

0x6ca43f…c331

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x91220b8f…7a04

0x1b6862…e19c

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 0x0000000000…00003d

← previous block·next block →recent activity