Block #73,204,712

← previous blocknext block →recent activity

Analyzing

Block #73,204,712

10 transactions · 9 stateful · 2026-05-08 08:26:43 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,204,712  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x03b4cc12…6262

0x065c9d…c394

2 touches
0 conflicts

0x7969e7c7…8e89

0x065c9d…c394

2 touches
0 conflicts

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0xa36f5168…f85d

0x065c9d…c394

2 touches
0 conflicts

0xc7f973f6…5996

0x065c9d…c394

2 touches
0 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

3 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity