← previous blocknext block →recent activity

Analyzing

Block #74,511,033

11 transactions · 9 stateful · 2026-05-14 09:38:27 UTC

Parallelism

55/100

Blocked

44%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,511,033  ·  11 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x0872abbe…9c39

0x2a68ba…90c5

4 touches
1 conflict

0xaaa31ee1…17a8

0xd32edf…ff58

3 touches
1 conflict

0x490b34bd…61d7

0x065c9d…c394

3 touches
1 conflict

0xd15a52b5…2f77

0x065c9d…c394

3 touches
1 conflict

0x42fda0f8…68b4

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity