← previous blocknext block →recent activity

Analyzing

Block #74,346,800

32 transactions · 24 stateful · 2026-05-13 15:24:38 UTC

Parallelism

69/100

Blocked

63%

Avg conflicts / tx

1.47

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,346,800  ·  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

0x62d080e9…4a7c

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0x313f2565…5b00

0x34b655…2a6f

10 touches
10 conflicts

0x55888ede…6745

0x34b655…2a6f

10 touches
10 conflicts

0x5d70606a…1d53

0x34b655…2a6f

10 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

10 touches
10 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

10 touches
10 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 0x62d080e928…5a4a7c

← previous block·next block →recent activity