← previous blocknext block →recent activity

Analyzing

Block #73,649,738

24 transactions · 22 stateful · 2026-05-10 09:49:27 UTC

Parallelism

67/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,649,738  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0xced1c5fb…6e5b

0xd32edf…ff58

5 touches
3 conflicts

0xbcdaffab…78f3

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

← previous block·next block →recent activity