← previous blocknext block →recent activity

Analyzing

Block #74,326,348

12 transactions · 10 stateful · 2026-05-13 13:08:38 UTC

Parallelism

75/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,326,348  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24d866cf…b001

0x065c9d…c394

4 touches
1 conflict

0xcecdaebc…3d59

0x065c9d…c394

3 touches
1 conflict

0xeb813d57…4631

0x065c9d…c394

3 touches
1 conflict

0xf7f50373…ceff

0x065c9d…c394

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 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: 0x065c9d28…a9c394

3 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity