← previous blocknext block →recent activity

Analyzing

Block #75,479,203

13 transactions · 9 stateful · 2026-05-18 21:29:47 UTC

Parallelism

69/100

Blocked

44%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,479,203  ·  13 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

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 conflicts

0x31dd6c98…b24c

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065d

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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: 0x188d586d…f9ea8e

3 conflicts on slot 0xe75ce68176…09ba5f

← previous block·next block →recent activity