← previous blocknext block →recent activity

Analyzing

Block #75,839,722

27 transactions · 20 stateful · 2026-05-20 13:41:37 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,839,722  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x74e485b1…d380

0x34b655…2a6f

4 touches
1 conflict

0x0e084053…0157

0xd32edf…ff58

3 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

2 touches
0 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)

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity