← previous blocknext block →recent activity

Analyzing

Block #73,922,341

32 transactions · 30 stateful · 2026-05-11 16:18:32 UTC

Parallelism

69/100

Blocked

60%

Avg conflicts / tx

1.88

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,922,341  ·  32 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x9d652ee8…83ca

0x34b655…2a6f

8 touches
6 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0xfac61869…a55c

0x1b6862…e19c

6 touches
3 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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity