← previous blocknext block →recent activity

Analyzing

Block #75,091,824

8 transactions · 7 stateful · 2026-05-17 02:21:19 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,091,824  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfab2346f…2816

0x065c9d…c394

4 touches
1 conflict

0x328467ef…ca4a

0x065c9d…c394

3 touches
1 conflict

0x21b9936e…76d4

0x065c9d…c394

3 touches
1 conflict

0x87d13911…d4c1

0x065c9d…c394

2 touches
0 conflicts

0x89077196…e045

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

2 touches
0 conflicts

0xfa84a867…616e

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 0x0000000000…00003d

← previous block·next block →recent activity