Block #73,201,621

← previous blocknext block →recent activity

Analyzing

Block #73,201,621

24 transactions · 23 stateful · 2026-05-08 08:06:10 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

1.17

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,201,621  ·  24 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

0xb99d4c43…d17d

0xd32edf…ff58

9 touches
10 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd9f18d9a…141d

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: 0xd32edf66…9fff58

10 conflicts on slot 0xb99d4c436b…6bd17d

← previous block·next block →recent activity