← previous blocknext block →recent activity

Analyzing

Block #74,951,867

16 transactions · 14 stateful · 2026-05-16 10:45:57 UTC

Parallelism

63/100

Blocked

36%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,951,867  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfcb7b8b2…ebb3

0x065c9d…c394

8 touches
6 conflicts

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x6783c424…e246

0xd32edf…ff58

3 touches
1 conflict

0xa48fbdc5…eb96

0x065c9d…c394

3 touches
1 conflict

0x22212696…db7b

0x065c9d…c394

3 touches
1 conflict

0xda650f3d…8685

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