← previous blocknext block →recent activity

Analyzing

Block #75,727,978

19 transactions · 16 stateful · 2026-05-20 01:17:07 UTC

Parallelism

84/100

Blocked

38%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,727,978  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xb7b446d2…2006

0x34b655…2a6f

6 touches
3 conflicts

0xb982d87d…3c8d

0xd32edf…ff58

5 touches
3 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0xdfa159d0…1576

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xcd4d0c58…99c6

0x1b6862…e19c

4 touches
1 conflict

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)

3 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity