← previous blocknext block →recent activity

Analyzing

Block #75,842,501

17 transactions · 14 stateful · 2026-05-20 14:00:19 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,842,501  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xa6e2f5ab…5550

0x065c9d…c394

4 touches
1 conflict

0x0aa885fa…a3d1

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0x3666bf…c52f

4 touches
1 conflict

0x00000000…0000

0x614b85…a284

2 touches
0 conflicts

0x00000000…0003

0x614b85…a284

2 touches
0 conflicts

0x00000000…0004

0x614b85…a284

2 touches
0 conflicts

0x00000000…0009

0x614b85…a284

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)

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity