Block #73,399,779

← previous blocknext block →recent activity

Analyzing

Block #73,399,779

32 transactions · 27 stateful · 2026-05-09 06:04:28 UTC

Parallelism

88/100

Blocked

37%

Avg conflicts / tx

0.66

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,399,779  ·  32 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0xdffcb9ae…f861

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity