← previous blocknext block →recent activity

Analyzing

Block #75,503,290

25 transactions · 20 stateful · 2026-05-19 00:15:05 UTC

Parallelism

88/100

Blocked

30%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,503,290  ·  25 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

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0xc49de867…d5c7

0x754704…b603

4 touches
1 conflict

0xa4c5ffcb…c568

0x065c9d…c394

2 touches
0 conflicts

0xd1394a1f…b33e

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 0x443a3e479f…3af4a4

← previous block·next block →recent activity