← previous blocknext block →recent activity

Analyzing

Block #74,527,144

14 transactions · 13 stateful · 2026-05-14 11:26:58 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,527,144  ·  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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x554f1ada…6916

0x5d823e…89c6

4 touches
1 conflict

0x3e4b02f8…bf0d

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

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 0x47b807a243…c53307

← previous block·next block →recent activity