← previous blocknext block →recent activity

Analyzing

Block #74,409,534

31 transactions · 25 stateful · 2026-05-13 22:22:10 UTC

Parallelism

87/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,409,534  ·  31 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

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0xd6453e11…c54e

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x1c62ed72…6bc5

0xd32edf…ff58

5 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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

6 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity