Block #73,318,603

← previous blocknext block →recent activity

Analyzing

Block #73,318,603

21 transactions · 14 stateful · 2026-05-08 21:04:24 UTC

Parallelism

81/100

Blocked

43%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,318,603  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x5d59a17d…63ed

0xa6afd3…d132

3 touches
1 conflict

0x68817920…a929

0x065c9d…c394

3 touches
1 conflict

0xa109d03f…64e0

0x0594c7…a3be

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity