← previous blocknext block →recent activity

Analyzing

Block #74,351,734

39 transactions · 30 stateful · 2026-05-13 15:57:21 UTC

Parallelism

74/100

Blocked

57%

Avg conflicts / tx

1.26

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,351,734  ·  39 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

14 touches
21 conflicts

0xf5ce487b…9cca

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x908d4442…2c4b

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x4a7b4bbc…a9bf

0xd32edf…ff58

9 touches
10 conflicts

0x99f080dc…58c1

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

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

21 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity