← previous blocknext block →recent activity

Analyzing

Block #73,663,977

17 transactions · 12 stateful · 2026-05-10 11:25:20 UTC

Parallelism

88/100

Blocked

17%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,663,977  ·  17 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x20e4cf5b…e1dc

0xd32edf…ff58

3 touches
1 conflict

0xa1b3dbbd…eb00

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0x74fe76c9…225f

0x3bd359…433a

2 touches
0 conflicts

0xb1acfe51…c6b1

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity