← previous blocknext block →recent activity

Analyzing

Block #75,191,266

13 transactions · 10 stateful · 2026-05-17 13:25:01 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,191,266  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6bd04356…724b

0x065c9d…c394

4 touches
1 conflict

0x98861554…5e85

0x065c9d…c394

3 touches
1 conflict

0x043e9d72…83fd

0x065c9d…c394

3 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x5c7bc1b9…4ced

0x065c9d…c394

2 touches
0 conflicts

0xa1c4251c…1842

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

1 conflict on slot 0x6bd04356c8…4e724b

← previous block·next block →recent activity