← previous blocknext block →recent activity

Analyzing

Block #73,383,471

11 transactions · 10 stateful · 2026-05-09 04:15:51 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,383,471  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xa9f94c2a…ea84

0x065c9d…c394

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x4fa07476…4080

0x065c9d…c394

4 touches
1 conflict

0x27d2c8bb…9f35

0x065c9d…c394

3 touches
1 conflict

0xd5c7aa85…3454

0x065c9d…c394

2 touches
0 conflicts

0xe173c3fb…309a

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity