← previous blocknext block →recent activity

Analyzing

Block #74,565,854

14 transactions · 11 stateful · 2026-05-14 15:48:17 UTC

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,565,854  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x551a9aa1…39d4

0x065c9d…c394

3 touches
1 conflict

0x0cc44f4b…0cf0

0x065c9d…c394

3 touches
1 conflict

0xee7579ed…f620

0x065c9d…c394

3 touches
1 conflict

0x2e831a3a…ad0c

0x065c9d…c394

3 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x06c10d86…6883

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity