Block #73,334,505

← previous blocknext block →recent activity

Analyzing

Block #73,334,505

10 transactions · 9 stateful · 2026-05-08 22:50:08 UTC

Parallelism

50/100

Blocked

44%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,334,505  ·  10 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

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf9caebba…15b3

0x065c9d…c394

4 touches
1 conflict

0xd03ffce1…113a

0x065c9d…c394

3 touches
1 conflict

0x3143e0a9…ada3

0x065c9d…c394

3 touches
1 conflict

0x077ad2c8…b578

0x065c9d…c394

3 touches
1 conflict

0x0d3c7cd0…8a16

0x065c9d…c394

3 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity