← previous blocknext block →recent activity

Analyzing

Block #74,454,421

41 transactions · 23 stateful · 2026-05-14 03:20:55 UTC

Parallelism

88/100

Blocked

52%

Avg conflicts / tx

0.49

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,454,421  ·  41 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xa64a8016…490a

0xd32edf…ff58

7 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x9ec1983e…f08f

0x34b655…2a6f

6 touches
3 conflicts

0xc0f25d9d…67d1

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity