← previous blocknext block →recent activity

Analyzing

Block #75,479,006

34 transactions · 26 stateful · 2026-05-18 21:28:24 UTC

Parallelism

85/100

Blocked

42%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,479,006  ·  34 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x846f2172…fd54

0x0555e3…2b9c

10 touches
10 conflicts

0x8f1dbe88…8e36

0xee8c0e…1242

8 touches
6 conflicts

0x34df2ee5…ab49

0x754704…b603

8 touches
6 conflicts

0x00000000…0000

0xca50b9…1d03

8 touches
6 conflicts

0x00000000…0003

0xca50b9…1d03

8 touches
6 conflicts

0x00000000…0004

0xca50b9…1d03

8 touches
6 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

8 touches
6 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

10 conflicts on slot 0xe75ce68176…09ba5f

← previous block·next block →recent activity