Block #73,334,373

← previous blocknext block →recent activity

Analyzing

Block #73,334,373

8 transactions · 6 stateful · 2026-05-08 22:49:17 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,334,373  ·  8 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

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5e6b48f5…fa40

0x065c9d…c394

2 touches
0 conflicts

0x790bb4d2…811a

0x065c9d…c394

2 touches
0 conflicts

0x88d8f3bb…4ea6

0x065c9d…c394

2 touches
0 conflicts

0xa1ccc58e…7d88

0x065c9d…c394

2 touches
0 conflicts

0x1dc64986…6555

0x34b655…2a6f

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 0xf537eaa0c6…3873c8

← previous block·next block →recent activity