← previous blocknext block →recent activity

Analyzing

Block #74,956,995

34 transactions · 25 stateful · 2026-05-16 11:20:25 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,956,995  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3e49348b…9445

0x34b655…2a6f

16 touches
28 conflicts

0xba38536d…2b7d

0x065c9d…c394

10 touches
10 conflicts

0x35b65947…44d1

0xc8689a…ee79

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

8 touches
6 conflicts

0x7457fde9…560a

0x34b655…2a6f

8 touches
6 conflicts

0x8aa1941d…2988

0x34b655…2a6f

8 touches
6 conflicts

0xa8bd52b5…862e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

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

28 conflicts on slot 0x3e49348b38…839445

← previous block·next block →recent activity