← previous blocknext block →recent activity

Analyzing

Block #73,867,322

13 transactions · 12 stateful · 2026-05-11 10:12:02 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,867,322  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7f81fb82…633e

0x065c9d…c394

5 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

2 touches
0 conflicts

0xe0a9b70c…c027

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

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 0x7f81fb82c1…ec633e

← previous block·next block →recent activity