← previous blocknext block →recent activity

Analyzing

Block #75,479,186

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

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

12 touches
15 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

10 touches
10 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 conflicts

0x08f4c240…db35

0x754704…b603

6 touches
3 conflicts

0xe75ce681…ba60

0x188d58…ea8e

6 touches
3 conflicts

0x62c3bcda…93a5

0x754704…b603

6 touches
3 conflicts

0x139ad71a…8429

0xd18b7e…414b

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

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity