← previous blocknext block →recent activity

Analyzing

Block #75,254,474

7 transactions · 6 stateful · 2026-05-17 20:27:04 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,254,474  ·  7 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

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbf5097bb…4a30

0x065c9d…c394

3 touches
1 conflict

0x225d286c…a413

0x065c9d…c394

2 touches
0 conflicts

0x56c5c388…843a

0x065c9d…c394

2 touches
0 conflicts

0x57c3a64f…2e64

0x065c9d…c394

2 touches
0 conflicts

0x97dbf8c6…58c5

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 0xfe2bac2b2f…482cec

← previous block·next block →recent activity