← previous blocknext block →recent activity

Analyzing

Block #73,795,722

22 transactions · 20 stateful · 2026-05-11 02:14:25 UTC

Parallelism

68/100

Blocked

65%

Avg conflicts / tx

1.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,795,722  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x5de96bd3…c60c

0x34b655…2a6f

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xd0d1435f…56f7

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x5d70606a…1d53

0x34b655…2a6f

8 touches
6 conflicts

0x7cbd466f…1700

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

15 conflicts on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity