← previous blocknext block →recent activity

Analyzing

Block #74,403,213

11 transactions · 9 stateful · 2026-05-13 21:40:04 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,403,213  ·  11 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9b36f19f…fa5a

0x34b655…2a6f

4 touches
1 conflict

0xa05dafe7…aff6

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x6eba4796…14af

0x065c9d…c394

2 touches
0 conflicts

0xa215d0ab…5d95

0x065c9d…c394

2 touches
0 conflicts

0xba809423…9b52

0x065c9d…c394

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity