← previous blocknext block →recent activity

Analyzing

Block #75,233,089

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

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,233,089  ·  10 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe5ea0ae3…25ec

0x065c9d…c394

4 touches
1 conflict

0xeca423df…af08

0x065c9d…c394

4 touches
1 conflict

0x23fa36a2…52f4

0x065c9d…c394

3 touches
1 conflict

0x3cbe2f13…1799

0x065c9d…c394

3 touches
1 conflict

0x72db7ba2…71f4

0x065c9d…c394

3 touches
1 conflict

0xaf93b776…1afb

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity