← previous blocknext block →recent activity

Analyzing

Block #75,478,941

37 transactions · 25 stateful · 2026-05-18 21:27:56 UTC

Parallelism

86/100

Blocked

36%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,478,941  ·  37 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

8 touches
6 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

6 touches
3 conflicts

0x00000000…0000

0x094452…0a09

6 touches
3 conflicts

0x00000000…0004

0x094452…0a09

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x751db0c0…4f57

0xd18b7e…414b

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

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: USDC (USDC)

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity