← previous blocknext block →recent activity

Analyzing

Block #74,527,201

11 transactions · 9 stateful · 2026-05-14 11:27:22 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,527,201  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xb6144afb…f471

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xdf33c32c…667f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xc5b778d2…a901

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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

1 conflict on slot 0xb6144afbe7…adf471

← previous block·next block →recent activity