← previous blocknext block →recent activity

Analyzing

Block #73,653,435

13 transactions · 11 stateful · 2026-05-10 10:14:16 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,653,435  ·  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

0xd7d96113…be05

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x49f5c127…52b7

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xa349d489…7546

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

3 conflicts on slot 0xd7d96113db…edbe05

← previous block·next block →recent activity