← previous blocknext block →recent activity

Analyzing

Block #75,478,970

29 transactions · 19 stateful · 2026-05-18 21:28:09 UTC

Parallelism

79/100

Blocked

53%

Avg conflicts / tx

0.66

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,478,970  ·  29 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

0x00f7e3b7…e015

0x188d58…ea8e

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x46cb45de…a566

0x188d58…ea8e

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a568

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

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

6 conflicts on slot 0x00f7e3b74f…eee015

← previous block·next block →recent activity