Block #73,201,255

← previous blocknext block →recent activity

Analyzing

Block #73,201,255

10 transactions · 8 stateful · 2026-05-08 08:03:43 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x176a927e…ff5e

0x065c9d…c394

2 touches
0 conflicts

0x2e4f1565…f1c3

0x065c9d…c394

2 touches
0 conflicts

0x953e0115…0c1f

0x065c9d…c394

2 touches
0 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

2 touches
0 conflicts

0xf6c0a500…89e6

0x065c9d…c394

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

6 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity