Block #73,211,267

← previous blocknext block →recent activity

Analyzing

Block #73,211,267

11 transactions · 10 stateful · 2026-05-08 09:10:18 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,211,267  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xdd9f8311…bc39

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x191e602b…40e8

0x065c9d…c394

2 touches
0 conflicts

0x3beda465…0bdd

0x065c9d…c394

2 touches
0 conflicts

0x4027098f…b329

0x065c9d…c394

2 touches
0 conflicts

0x4f51f21a…47b5

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

1 conflict on slot 0xdd9f8311d0…b3bc39

← previous block·next block →recent activity