← previous blocknext block →recent activity

Analyzing

Block #75,066,674

10 transactions · 7 stateful · 2026-05-16 23:33:07 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,066,674  ·  10 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

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4969cbc3…9d0c

0x065c9d…c394

2 touches
0 conflicts

0x55e8ea86…7971

0x065c9d…c394

2 touches
0 conflicts

0x699a1eef…93d3

0x065c9d…c394

2 touches
0 conflicts

0x72e0581f…5cb2

0x065c9d…c394

2 touches
0 conflicts

0x81c2d283…5934

0x065c9d…c394

2 touches
0 conflicts

0x9707c75b…072b

0x065c9d…c394

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 0x348fda08cf…fc7e96

← previous block·next block →recent activity