← previous blocknext block →recent activity

Analyzing

Block #75,507,089

30 transactions · 19 stateful · 2026-05-19 00:41:09 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,507,089  ·  30 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

0xb1cfe36d…3c01

0xd32edf…ff58

9 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 conflicts

0x09beabbc…065c

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: 0xd32edf66…9fff58

10 conflicts on slot 0xb1cfe36d1d…5c3c01

← previous block·next block →recent activity