← previous blocknext block →recent activity

Analyzing

Block #75,105,449

8 transactions · 7 stateful · 2026-05-17 03:52:06 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,105,449  ·  8 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

6 touches
3 conflicts

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x51ffd6eb…3afc

0x065c9d…c394

4 touches
1 conflict

0x2bf95f46…63d3

0x065c9d…c394

4 touches
1 conflict

0xc424b137…a613

0x065c9d…c394

3 touches
1 conflict

0xb32ccdc1…d408

0x065c9d…c394

3 touches
1 conflict

0xc61bcbac…e34b

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

3 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity