← previous blocknext block →recent activity

Analyzing

Block #75,116,774

16 transactions · 14 stateful · 2026-05-17 05:07:45 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,116,774  ·  16 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

0x12c575f4…a0a6

0x065c9d…c394

6 touches
3 conflicts

0x9e8d90b4…1e76

0x065c9d…c394

5 touches
3 conflicts

0xc2bed07d…6069

0xd32edf…ff58

5 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa199729f…712d

0x065c9d…c394

3 touches
1 conflict

0x09d2cc9d…cc79

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 0x12c575f434…44a0a6

← previous block·next block →recent activity