← previous blocknext block →recent activity

Analyzing

Block #75,479,190

35 transactions · 23 stateful · 2026-05-18 21:29:42 UTC

Parallelism

91/100

Blocked

39%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,479,190  ·  35 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xcba203ee…68a3

0xd32edf…ff58

5 touches
3 conflicts

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

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

3 conflicts on slot 0xcba203ee4d…fd68a3

← previous block·next block →recent activity