← previous blocknext block →recent activity

Analyzing

Block #75,056,637

12 transactions · 9 stateful · 2026-05-16 22:26:14 UTC

Parallelism

58/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,056,637  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x4d70912f…327a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5ff8daba…5c1e

0xd32edf…ff58

3 touches
1 conflict

0xf648060d…658f

0x065c9d…c394

3 touches
1 conflict

0x22c23ce0…dda3

0x065c9d…c394

3 touches
1 conflict

0xabf8c969…260d

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 0x348fda08cf…fc7e96

← previous block·next block →recent activity