← previous blocknext block →recent activity

Analyzing

Block #75,231,435

9 transactions · 9 stateful · 2026-05-17 17:53:18 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,231,435  ·  9 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

0xa6c55366…29a1

0x065c9d…c394

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x032fdd29…e488

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa0791758…d6a1

0x065c9d…c394

4 touches
1 conflict

0x90d90757…1d3f

0x065c9d…c394

3 touches
1 conflict

0x3b83d1a9…073d

0x065c9d…c394

3 touches
1 conflict

0x4e8681c6…eedd

0x065c9d…c394

3 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: 0x065c9d28…a9c394

1 conflict on slot 0xa6c553661b…4d29a1

← previous block·next block →recent activity