← previous blocknext block →recent activity

Analyzing

Block #74,352,084

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

Parallelism

72/100

Blocked

67%

Avg conflicts / tx

1.56

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,352,084  ·  32 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0x111f72de…b33c

0x34b655…2a6f

6 touches
3 conflicts

0x4f483049…3cc7

0x34b655…2a6f

6 touches
3 conflicts

0x5caf9f43…a348

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 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