Block #73,211,201

← previous blocknext block →recent activity

Analyzing

Block #73,211,201

26 transactions · 21 stateful · 2026-05-08 09:09:51 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0xd8a8b382…fb50

0xd32edf…ff58

9 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0xde4b0aeb…ddc2

0x065c9d…c394

4 touches
1 conflict

0x56d15fef…80ac

0x065c9d…c394

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

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 0xd8a8b38252…89fb50

← previous block·next block →recent activity