← previous blocknext block →recent activity

Analyzing

Block #73,920,940

31 transactions · 19 stateful · 2026-05-11 16:09:13 UTC

Parallelism

68/100

Blocked

68%

Avg conflicts / tx

1.65

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,920,940  ·  31 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

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

10 touches
10 conflicts

0x03df3a18…58e7

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0xee230b20…5a0f

0x34b655…2a6f

10 touches
10 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity