← previous blocknext block →recent activity

Analyzing

Block #73,649,947

10 transactions · 9 stateful · 2026-05-10 09:50:51 UTC

Parallelism

50/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,649,947  ·  10 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xbd4fcdeb…f7ee

0x065c9d…c394

3 touches
1 conflict

0x4f63a30e…1687

0x065c9d…c394

2 touches
0 conflicts

0x5a49f95f…bbc3

0x065c9d…c394

2 touches
0 conflicts

0x6a744db0…9b35

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity