Block #73,201,575

← previous blocknext block →recent activity

Analyzing

Block #73,201,575

24 transactions · 18 stateful · 2026-05-08 08:05:52 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x27b2ed5e…2fc7

0xd32edf…ff58

7 touches
6 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x400c70d5…c80c

0x065c9d…c394

5 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x251861eb…78fd

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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

6 conflicts on slot 0x27b2ed5eb8…d72fc7

← previous block·next block →recent activity