← previous blocknext block →recent activity

Analyzing

Block #75,098,039

17 transactions · 10 stateful · 2026-05-17 03:02:39 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,098,039  ·  17 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

0x443a3e47…f4a4

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x118047da…4dd8

0x065c9d…c394

3 touches
1 conflict

0x030eb8d9…44bf

0x065c9d…c394

3 touches
1 conflict

0x20cc2272…88dc

0x34b655…2a6f

2 touches
0 conflicts

0x4118bd12…924a

0x34b655…2a6f

2 touches
0 conflicts

0x4191fb08…b561

0x34b655…2a6f

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

6 conflicts on slot 0x443a3e479f…3af4a4

← previous block·next block →recent activity