← previous blocknext block →recent activity

Analyzing

Block #73,652,211

18 transactions · 11 stateful · 2026-05-10 10:06:01 UTC

Parallelism

78/100

Blocked

27%

Avg conflicts / tx

0.22

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,652,211  ·  18 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xeb830a48…f153

0xd32edf…ff58

3 touches
1 conflict

0x6315d884…e963

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0x99c3a0f2…5031

0x065c9d…c394

2 touches
0 conflicts

0x06cdf7f0…fbe6

0x3bd359…433a

2 touches
0 conflicts

0xb9eb1318…ce53

0x3bd359…433a

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity