← previous blocknext block →recent activity

Analyzing

Block #75,301,384

12 transactions · 11 stateful · 2026-05-18 01:41:20 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,301,384  ·  12 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

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0xe8f5e33f…719c

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x25b2726c…56ea

0x188d58…ea8e

2 touches
0 conflicts

0x847462fa…910f

0x188d58…ea8e

2 touches
0 conflicts

0x06e40499…165e

0x1d1325…2305

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

3 conflicts on slot 0xfcb7b8b239…6bebb3

← previous block·next block →recent activity