← previous blocknext block →recent activity

Analyzing

Block #74,346,768

23 transactions · 18 stateful · 2026-05-13 15:24:25 UTC

Parallelism

52/100

Blocked

61%

Avg conflicts / tx

2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,346,768  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

18 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x1c348b58…836a

0x34b655…2a6f

10 touches
10 conflicts

0x313f2565…5b00

0x34b655…2a6f

10 touches
10 conflicts

0x32ee90db…decc

0x34b655…2a6f

10 touches
10 conflicts

0x4f483049…3cc7

0x34b655…2a6f

10 touches
10 conflicts

0x55888ede…6745

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

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

36 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity