← previous blocknext block →recent activity

Analyzing

Block #75,262,098

10 transactions · 9 stateful · 2026-05-17 21:18:18 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,262,098  ·  10 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

0x085cf543…e478

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x713732b4…8dac

0x065c9d…c394

3 touches
1 conflict

0xd57a8b8f…5083

0x065c9d…c394

3 touches
1 conflict

0x38977271…9306

0x065c9d…c394

2 touches
0 conflicts

0x6b2cce7b…b657

0x065c9d…c394

2 touches
0 conflicts

0xbe7e7529…2c42

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x085cf5437d…13e478

← previous block·next block →recent activity