Block #73,211,431

← previous blocknext block →recent activity

Analyzing

Block #73,211,431

13 transactions · 11 stateful · 2026-05-08 09:11:23 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,211,431  ·  13 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

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2637dcf3…37a7

0x065c9d…c394

2 touches
0 conflicts

0x7fd0f1c0…cee4

0x065c9d…c394

2 touches
0 conflicts

0x987453b0…618a

0x065c9d…c394

2 touches
0 conflicts

0xe258c31c…f4ab

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xce7bfe5ef1…205e58

← previous block·next block →recent activity