← previous blocknext block →recent activity

Analyzing

Block #75,079,760

17 transactions · 13 stateful · 2026-05-17 01:00:37 UTC

Parallelism

82/100

Blocked

23%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,079,760  ·  17 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

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x059e2e88…8d37

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

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

1 conflict on slot 0xba38536db1…342b7d

← previous block·next block →recent activity