← previous blocknext block →recent activity

Analyzing

Block #74,415,900

17 transactions · 16 stateful · 2026-05-13 23:04:29 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,415,900  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065d

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity